Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 88948 invoked from network); 24 Nov 2000 01:38:15 -0000 Received: from cochrane.krankikom.de (194.77.169.5) by locus.apache.org with SMTP; 24 Nov 2000 01:38:15 -0000 Received: from platt ([194.77.169.59]) by cochrane.krankikom.de (8.9.3/8.9.3) with SMTP id CAA23476 for ; Fri, 24 Nov 2000 02:38:09 +0100 From: "Paulo Gaspar" To: Subject: RE: [PROPOSAL] Tomcat 4.0 Milestone 5 Date: Fri, 24 Nov 2000 02:48:32 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Pier P. Fumagalli [mailto:pier@betaversion.org] > Sent: Friday, November 24, 2000 01:25 > > GOMEZ Henri wrote: > > > > It seems clear for you that Tomcat 3.2 (and the full 3.x line) > > are allready products in end of life. > > Don't want to get back on the discussion _AGAIN_ ... > > > But did they even have the time to start their 'production life' ? > > That's not Craig's fault, I believe... > > > I'm sorry to say but THERE IS STILL NO STABLE TOMCAT RELEASE. > > It's not Craig's fault... Nor of anyone on the current 4.x track... And probably it is no one's fault anyway. Some people blame it on lack of focus, but it would be a shame to completely cut new evolutions like Catalina until everything gets stable on Tomcat 3.2. Even because finding bugs is not necessarily a job for the some guys that are coding. And also because bugs need time to be detected. About the end of life of Tomcat 3.2, let's highlight the fact that Craig - one of (or THE) main developers of Tomcat 4, is putting a lot of effort on getting 3.2 out. This can have many reason, but a probable one is that he too believes that it is possible to get a Production Ready Tomcat 3.2 before getting a Production Ready 4.0. Remember: bugs need time to be detected and 3.2 already had more of such time. I like the harmony we had in this list during the last few weeks between the main defenders of Tomcat 3.x and of Tomcat 4. I would like it to stay that way. Both lines have its usefulness (3.3 included in the pack). We are having an effort on getting a Production Ready 3.2 NOW by the same people that are fighting for new evolutions. Isn't this the way it should be? As a user, I like this - and I bet I am not the only one. This ensures me that I will have a production ready Tomcat soon (I am still using JServ for that) and that Tomcat is, at the same time, evolving and improving. Isn't this that users want? Have fun, Paulo Gaspar