Kalnichevski, Oleg wrote:

If it is just about release numbers, let us call it HttpClient 3.0

Amen. I'm not sure how much point there is in a 2.1 release if there's not allowed to be *any* API breakage. Maybe we should freeze the 2.0 stream and just put out 2.0.1, etc. bug fix releases and call the current main trunk 3.0 so that we can clean up some of this stuff.

I think it might still pay to do some of it gradually, like the current exception fixes in "3.0" and the removal of the IOException inheritance in "4.0" so that the transitions are easuer. But I don't think we should be striving for 100% API compatibility in the next release.

-- Laura


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to