Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
To: tomcat-dev@jakarta.apache.org
From: Costin Manolache <cmanolache@yahoo.com>
Subject: Re: [5.0] Schedule change
Date: Tue, 30 Sep 2003 12:42:48 -0700
Lines: 25
Message-ID: <blcm1m$3fd$1@sea.gmane.org>
References: <009f01c3875d$5567f350$6480fea9@AMYROH>
 <3F79AA38.4000609@apache.org> <3F79B230.5030004@apache.org>
 <3F79BD2F.4050000@apache.org> <3F79CB15.5060401@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
User-Agent: KNode/0.7.2
Sender: news <news@sea.gmane.org>

Remy Maucherat wrote:

> Hi,
> 
> The signals I'm getting from Sun about the schedule of the
> specifications is highly confusing. Since I'm tired of having Tomcat
> depend on these, I propose taking advantage of the backwards
> compatibility of the spec, and replacing the TC 5 statement phrase with:
> 
> The 5.x releases implement the Servlet 2.3 and JSP 1.2 specifications,
> and will add support for the Servlet 2.4 and JSP 2.0 as soon as they are
> officially available.
> 
> That would allow making a timely 5.0 release, rather than expecting
> stuff for an indefinite amount of time ...
> 
> If I don't get yelled at too much, I'll call for a vote on this.
> 
> Comments ?

What about releasing it as tomcat4.2 ( since many people assume 4.x is the
implementation series for servlet 2.3 ) ? 

Costin