Return-Path: 
 <commons-dev-return-27251-qmlist-jakarta-archive-commons-dev=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@apache.org
Received: (qmail 95596 invoked from network); 2 Apr 2003 22:14:52 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 2 Apr 2003 22:14:52 -0000
Received: (qmail 3489 invoked by uid 97); 2 Apr 2003 22:16:46 -0000
Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org
Received: (qmail 3482 invoked from network); 2 Apr 2003 22:16:46 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 2 Apr 2003 22:16:46 -0000
Received: (qmail 95359 invoked by uid 500); 2 Apr 2003 22:14:50 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 95345 invoked from network); 2 Apr 2003 22:14:50 -0000
Received: from vpn1.seagullsw.com (HELO atlanta.seagullsw.com) (12.6.96.4)
  by daedalus.apache.org with SMTP; 2 Apr 2003 22:14:50 -0000
Received: by atlanta.seagullsw.com with Internet Mail Service (5.5.2656.59)
	id <H03Q4RXX>; Wed, 2 Apr 2003 17:16:32 -0500
Message-ID: <245A7290F0E0D311BF6E009027E7908B072043A1@atlanta.seagullsw.com>
From: Gary Gregory <ggregory@seagullsw.com>
To: 'Jakarta Commons Developers List' <commons-dev@jakarta.apache.org>
Subject: RE: [codec] promote from sandbox
Date: Wed, 2 Apr 2003 17:16:21 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2F965.7DBB8690"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C2F965.7DBB8690
Content-Type: text/plain

<Ryan Hoegg>Does anyone have an opinion on what they'd like to see in Codec
before a release? </Ryan Hoegg>

FYI, our only requirement right now is for a Base64 class. We use three
different ones so far (don't ask).

Gary

-----Original Message-----
From: Ryan Hoegg [mailto:rhoegg@isisnetworks.net] 
Sent: Wednesday, April 02, 2003 11:53 AM
To: Jakarta Commons Developers List
Subject: Re: [codec] promote from sandbox

Just read the etiquette thing.  I think a good indicator that Codec 
Base64 is ready for consumption is its successful integration in both 
HttpClient and XML-RPC.  I see that it is used in many more projects, 
but those are the two who have been active recently.  Once we have two 
projects using it, I imagine other projects will be more likely to jump 
on board.

However, Base64's readiness for consumption is probably not enough to 
warrant Codec's promotion by itself.

Does anyone have an opinion on what they'd like to see in Codec before a 
release?  Tim's documentation on an architecture roadmap is a good 
start, imho.

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net

Stephen Colebourne wrote:

>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...
>
>Stephen
>  
>



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

------_=_NextPart_001_01C2F965.7DBB8690--