Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 35126 invoked from network); 5 May 2006 16:23:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 May 2006 16:23:09 -0000 Received: (qmail 67769 invoked by uid 500); 5 May 2006 16:23:03 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 67701 invoked by uid 500); 5 May 2006 16:23:02 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 67689 invoked by uid 99); 5 May 2006 16:23:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 09:23:02 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [195.227.30.246] (HELO datura.kippdata.de) (195.227.30.246) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 09:23:01 -0700 Received: from [195.227.30.148] (larix [195.227.30.148]) by datura.kippdata.de (8.13.5/8.13.5) with ESMTP id k45GMeEc016008 for ; Fri, 5 May 2006 18:22:40 +0200 (CEST) Message-ID: <445B7BD0.604@kippdata.de> Date: Fri, 05 May 2006 18:22:40 +0200 From: Rainer Jung User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: TC 6: What needs to be done? References: <25661524.398101146843106015.JavaMail.servlet@perfora> <445B72C7.5080208@ptc.com> In-Reply-To: <445B72C7.5080208@ptc.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N So people think it TC 6 should be focused on JEE 5 compatibility and other major changes should only be done, if they pose no risk on an early date. Somehow we are to late in the J2EE time frame. On the other hand, major changes to e.g. the configuration management should not be done for a release that looks like a minor release (6.1), because then users will be very irritated that they have to learn a very new configuration world. So as a consequence we might need to prepare for a TC 6.5 or TC 7 until end of this year? This will look strange at a first glance (why two major releases so shortly after each other), but if we decide to focus TC 6 on JEE 5 compatibility and early delivery it looks like a logical consequence. - Rainer Jess Holle wrote: > jacob@hookom.net wrote: > >> Would it be suitable to focus on JEE 5 compliance in the short run for >> a soon to be released TC 6, then enhance the value adds of TC for a >> 6.1 release later this year? >> > > That sounds a lot better to me... > > -- > Jess Holle > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org > For additional commands, e-mail: dev-help@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org