>I am working on the 3.x branch for about a year and made clear
>many times
>that I'll continue to work on it for a while. At least until it's the
>fastest and most secure servlet container ( we are close, but
>not there ).
>
>I see there is a lot of interest in killing 3.x and making it
>"EOL", but
>unless the Apache licence was changed overnight it will be
>difficult to do
>that.
Please dont kill , we need to have a clean 3.x branch. As I said previously
3.x must be for prod environment where SERVLET 2.2 / JSP 1.1 are
the de facto-standard
>Tomcat3.2 was ready months ago, but everyone kept fixing
>non-critical bugs
>that should have gone into 3.3 ( the development branch after the
>rules). I started working on the 3.3 as soon as 3.2 was "freezed" and
>Larry, Nacho and few other took care of checking in the patches and
>waiting for a release. There are some issues that can't be resolve in a
>"freezed" code, but only in the a development branch.
Yes, We saw many reference of code to be fixed on 3.3. Now that some want to
kill 3.3 and directly play with 4.0, the risk of having a 3.x branch
(the current branch) falling in 'unsupported software land' is VERY HIGH.
>Does it look like the 3.x branch is dead and nobody but Craig
>"is taking
>care of it" ????
Sorry but for now the only existing and used branch is 3.x (3.1 and 3.2b)
We need a URGENTLY a 3.2 release (with a bug lists) and start the 3.3 beta.
The rude question is, who need so quickly a TOMCAT 4.0 ?
Users, Apache Group, others ?
It may be time to ask not only developpers but users about what they want
first,
a stable and high performance servlet engine based on 3.x or development
release
based on 4.0 ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
