RE: [codec] promote from sandbox - RE: commons codec and Base64

On Wed, 2 Apr 2003, O'brien, Tim wrote: > I don't think it is a good policy to require backwards compatibility for > sandbox components, but I think we have a special case here since codec has > been in use for a sustained period of time. > Rarely is backwards compatiblity a bad thing. - Rod

RE: [codec] promote from sandbox - RE: commons codec and Base64

-- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 1:45 PM To: 'Jakarta Commons Developers List' Subject: RE: [codec] promote from sandbox - RE: commons codec and Base64 > -Original Message- > From: Stephen Colebourne [mailto:[EMAIL PROTECTED] &g

RE: [codec] promote from sandbox - RE: commons codec and Base64

> -Original Message- > From: Stephen Colebourne [mailto:[EMAIL PROTECTED] > > Promotion is probably a good idea, but it should be without > backwards compatability code IMO. You imply that there is a > codec 1.0 release, but this cannot be as sandbox components > may not have releases.

Re: [codec] promote from sandbox - RE: commons codec and Base64

i started a commons etiquette page on the wiki a little while ago which contains some opinions on the promotion process: http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaCommonsEtiquette it might of some help a little further down the line. - robert On Wednesday, April 2, 2003, at 07:07 PM,

[codec] promote from sandbox - RE: commons codec and Base64

Base64, Hex, Soundex, and Metaphone are stable and ready for consumption. The legacy Base64 implementation has been preserved in order to preserve backwards compatibility for projects which currently depend upon codec 1.0. http://jakarta.apache.org/commons/sandbox/codec/index.html Tim