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 92931 invoked from network); 27 Nov 2000 21:05:19 -0000 Received: from artemis.imaginet.fr (HELO mx2.imaginet.fr) (195.68.75.24) by locus.apache.org with SMTP; 27 Nov 2000 21:05:19 -0000 Received: from css5.cs (www2.slib.fr [195.68.49.130]) by mx2.imaginet.fr (8.9.3/8.8.8) with SMTP id WAA26367 for ; Mon, 27 Nov 2000 22:03:27 +0100 (MET) Received: from css4.cs (css4.cs [172.31.1.8]) by css5.cs (8.9.3/8.9.3) with ESMTP id WAA25566 for ; Mon, 27 Nov 2000 22:05:00 +0100 Received: from css6.cs ([172.31.1.170]) by css4.cs with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id XPVR1RP1; Mon, 27 Nov 2000 21:59:22 +0100 Received: (from nobody@localhost) by css6.cs (8.9.3/8.9.3) id VAA02166 for tomcat-dev@jakarta.apache.org; Mon, 27 Nov 2000 21:59:16 +0100 X-Authentication-Warning: css6.cs: nobody set sender to hgomez@slib.fr using -f To: tomcat-dev@jakarta.apache.org Subject: RE: [PROPOSAL] Tomcat 4.0 Milestone 5 Message-ID: <975358755.3a22cb23dba2a@css6.cs> Date: Mon, 27 Nov 2000 21:59:15 +0100 (CET) From: Gomez Henri References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.3 X-Originating-IP: 172.31.1.5 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > > It seems clear for you that Tomcat 3.2 (and the full 3.x line) > > are allready products in end of life. > > I don't know how you reached that conclusion, but I'm sure it's wrong - > tomcat 3.x is far from over :-) I just noticed that many of tomcat developers seems to focus only on TC 3.2 release and 4.0, but no more on 3.3. There is no support for 3.3 branch appart you and nacho (and a very little from me). > I know there is a lot of missinformation and confusions and interests, > but AFAIK development continues on 3.3 and probably will continue after > that ( we hope the core will be frozen after that - but it's not > because > it'll be "end of life" but because it'll be in a finally ready and we > can > start working on individual modules and new features ). I know it's an open source project and everyone can contribute but there will be 2 concurrents projects at Apache. May be not a good thing but will help give a substantial emulation between 3.3 and 4.0 teams. 4.0 appears to be a Sun Project (most of the active developpers on TC 4.0 branch are Sun employees). 3.3 seems a more open project. I saw that from outside... > An open source project is alive as long as people are using and > contributing to it - and there are many things that are developed right > now - and the code continue to be enhanced and improved. That's what > happen with tomcat 3.x. The question is now : Will 3.3 will restart from 3.2 release or must we try to reinject patch from 3.2 to 3.3. I could help on ajp13 stuff (both native mod_jk, mod_jserv and java ajp12/13). Regards