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 92689 invoked from network); 4 Jan 2001 19:43:08 -0000 Received: from unknown (HELO s1.servlets.net) (root@209.221.135.4) by h31.sny.collab.net with SMTP; 4 Jan 2001 19:43:08 -0000 Received: from gefionsoftware.com (IDENT:hans@lsanca1-ar8-071-096.biz.dsl.gtei.net [4.35.71.96]) by s1.servlets.net (8.9.3/8.9.3) with ESMTP id LAA15380 for ; Thu, 4 Jan 2001 11:43:05 -0800 Sender: hans@servlets.net Message-ID: <3A54D147.F2941D8A@gefionsoftware.com> Date: Thu, 04 Jan 2001 11:38:47 -0800 From: Hans Bergsten X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22 i686) X-Accept-Language: en-US MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: [VOTES] Tomcat 4.0-Beta-1 and New CVS Repositories References: <3A5220E0.45264058@eng.sun.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N "Craig R. McClanahan" wrote: > > Now that we've all recovered from New Years (and watched Oregon State teach > Notre Dame a few things about football -- go Beavers! :-), it's time to lay out > the next steps in Tomcat 4.0's lifetime. Here's what I propose: > > (1) Tomcat 4.0 Beta 1 > [...] propose to > create Tomcat 4.0 Beta 1 on Friday 5, 2001 -- after having a chance to integrate > a few more bug fixes for issues that were reported in the last couple of weeks. > [...] > The existing "jakarta-tomcat-4.0" repository will be branched with label > "tomcat_40_branch", and each 4.0.x beta and release will receive a label such as > "tomcat_40_b1". The "main" branch of this repository will be active for bug > fixes on 4.0, while major new development will shift to the 4.1 repository > described below. +1 > (2) Tomcat 4.1 Repository > [...] > Therefore, I propose to create a new "jakarta-tomcat-4.1" repository on Friday > as well, based originally on the code that is marked for Tomcat 4.0 beta 1. > [...] +1, now when I have seen the arguments for a new repository discussed in detail. > (3) New "jakarta-servletapi-4.0" CVS Repository > [...] +1, but I would (like others) prefer just "4" (or "4.x"), or "s22_j11" to use the spec versions instead. Another alternative is to name it based on the JSR that defines these APIs, i.e. "jsr053". Hans -- Hans Bergsten hans@gefionsoftware.com Gefion Software http://www.gefionsoftware.com Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com