"Pier P. Fumagalli" wrote:
>
> Sorry for starting what it might end up as a long flamewar, but reading
> almost 500 emails on the list I ended up a little confused... Also, in a
> bunch of side discussions, but related always to the same topic, I feel
> there's something wrong going around here...
Thanks Pier for bringing this issue to a vote. Based on the other replies
to this mail, it seems to me like the majority wants Tomcat 3.x to be the
RI for Servlet 2.2/JSP 1.1, with production quality of course, and
Tomcat 4.x the RI for Servlet 2.3/JSP 1.2. That's what makes most sense
to me. The devil may be in the details, but I hope we can make it so.
> [...]
> So, I'm proposing this plan, and please vote on 2 and 4 (1 and 3 were
> already voted upon with a bunch of +1s)...
>
> 1) Release Tomcat 3.2 final (soon, please!)
+1000.
Sam promised a release candidate a couple of weeks back, but it didn't
happen (I'm sure for a good reason). If Sam doesn't have the time to do
this now, maybe someone else who's familiar with the release procedures
can step up to the task?
When the release candidate is available, we should make sure it's tested
quickly (I promise to do so with a number of JSP applications I have handy).
Only serious regression bugs should be allowed to force another candidate
cycle.
For the future, I suggest we document the release procedures and put them
in CVS so it's easier for someone to help out with this if the appointed
release manager can't do it for any reason.
> 2) Create a new proposal tree alongside with Catalina (new name to avoid
> confusion, please)
-1, two code bases is more than enough ;-)
If we can agree that Tomcat 3.x is the RI for Servlet 2.2/JSP 1.1 *only*, it
makes sense for this code base to continue for bug fixes and improvements
that are in support of these spec versions. I would have preferred to call
these releases 3.2.1, 3.2.2 etc. instead of 3.3, but it's not all that
important.
Costin, Larry and others have put a lot of effort into 3.3, and even though
I have not tested it yet myself, based on comments from others it's much
better than 3.2 so lets take advantage of all that hard work and make
sure it's released as the next 2.2/1.1 RI instead of hiding it in a new
proposal branch.
> 3) Release Tomcat 4.0 (with Catalina, as we all decided)
+1, but this will take some time since the new specs will not be final
until next year, likely Q2.
> 4) Decide wether Tomcat 5.0 will be Catalina based or "whatever" new
> proposal comes along.
-1, let's focus on 3.x and 4.x for now.
Hans
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
