Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
From: hgo@slib.fr
To: tomcat-dev@jakarta.apache.org,
        "Craig R. McClanahan" <Craig.McClanahan@eng.sun.com>
Subject: Re: [PROPOSAL] Tomcat 4.0 Milestone 5
Message-ID: <975101218.3a1edd2275335@localhost.localdomain>
Date: Fri, 24 Nov 2000 22:26:58 +0100 (CET)
References: <361024C34A6DD2118689006097AE2B4DBFDCCC@css4.cs>
 <3A1EC8C6.E81AB1EF@eng.sun.com>
In-Reply-To: <3A1EC8C6.E81AB1EF@eng.sun.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.0

> > Your planning is to release TC 4.0 for late December or early January
> ?-)
> > What about Tomcat 3.2 release ? early December ?
> >
> 
> There have been several bug fixes posted for 3.2b8 that I want to
> evaluate, but
> no new critical bugs.  Therefore, my inclination will be to cut a final
> 3.2
> release next week, and start doing a maintenance cycle (3.2.1, 3.2.2,
> etc.) as
> needed -- we should discuss this more next week, after all the US folks
> get over
> their turkey hangovers ;-).

Many of the ajp13 bugs seems to be fixed (even the dreaded ajp13 + 
RequestDispatcher). 

I'm +1000 for the release and maintenance cycle. 
My question is about the 3.3-dev ? What will it became. I've got a huge
respect for Costin/Nacho works on 3.3-dev. What will it became ?
Will 3.2.1 will be based on 3.3-dev (yes not revolutin but realistic 
optimization) or just bug fixes of current 3.2b8.


> On 4.0 stability?  I don't think so.  You should consider me to be
> biased
> (Catalina has been *my* baby, after all :-), but I've seen the insides
> of 3.2
> and 4.0 in a lot more detail than I ever hoped to over the last month. 
> I have
> come to the following conclusions:
> 
> * The servlet container code in 3.2 is *substantially* better
>   than the servlet container code in 3.1 in terms of spec conformance,
>   number of bugs, functionality, and performance.
> 
> * The servlet container code in 4.0 is "more better" than 3.2
>   on spec compliance, at least as good on bug counts, and
>   at least as good on performance (soon to be better, because
>   Remy is working on optimizations on the HTTP/1.1 stack).
> 
> * The servlet container in 4.0 sports many additional features
>   over 3.2, and only lacks one at the moment -- the ability to
>   run a web app under a security manager.  That feature can be
>   added in 4.1, as soon as someone who understands this stuff
>   (Glenn, hint hint :-) can help make it happen.
> 
> * The JSP code in 3.2 and 4.0 is pretty equivalent, because we've
>   been tracking the bug fixes pretty well in parallel.