--- Remy Maucherat <[EMAIL PROTECTED]> wrote:
> This is not legal. Rodney's refactoring was never voted upon.
> Stable != released here. Stable means the API won't change in any
> significant way.
That is completely untrue. "Stable" means the API does what it was
intended to do. "Stable" means it has a well-defined set of tests and
criteria that the codebase will pass.
Just look at what you stated in the proposal!
"The package shall create and maintain a Java library implementing the
client side of the HTTP/1.1 protocol, as defined in RFC 2616 and RFC
2617. The package should : (a) Have an API which should be as simple to
use as possible, (b) Be as easy to extend as possible, (c) Provide
unconditional support for HTTP/1.1"
Under those considerations, http-client was never stable, and the
attempts by Rod, Morgan, Doug, and Vincent to use it have proved this.
If you want to keep your compatabilities, then revive the old code in
Slide (which should not have been decoupled until a commons 1.0 release
anyway).
But don't insist on releasing substandard code just to maintain a
low-grade status quo. And don't block any other approach for release
just because it's not "your way." That the code came from Slide does
not grant you special use privileges and API control.
There's plenty of room with Ant and Gump to make this work without
halting development for your project. The rest of us depend on a solid
release of http-client just as much as you do.
- Chuck
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
