Just call it 3.0. It's what you want, you'll feel better, and you won't waste time and effort doing minor improvements when you could instead focus on getting the API right (as you're going to do it anyway at some point, it seems pointless to waste time doing anything other than bugfixes -- should any be required! -- on 2.0).
- Chris ----- Original Message ----- From: "Michael Becke" <[EMAIL PROTECTED]> To: "Commons HttpClient Project" <[EMAIL PROTECTED]> Sent: Thursday, July 17, 2003 3:21 AM Subject: Re: [VOTE] Add commons-codec as an HttpClient dependency > > Not really. I am still fully behind the 2.1 release plan (as long as it > > remains about 'doing 2.0 more or less right', and not about second > > attempt at trying to work around the existing design limitations). > > However, if the pressure mounts to strictly follow the Jakarta release > > guidelines, I will strongly favour bypassing 2.1 release and going > > straight to 3.0 > > Yes, I agree. I may have been a little premature in bringing up the > issue. No-one seems to be complaining. Perhaps I am anticipating a > problem that will not arise. Either way I am glad it has been > discussed. > > Thank you, > > Mike > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
