Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 52486 invoked from network); 20 Aug 2004 15:26:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Aug 2004 15:26:56 -0000 Received: (qmail 1917 invoked by uid 500); 20 Aug 2004 15:26:44 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 1858 invoked by uid 500); 20 Aug 2004 15:26:43 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 1836 invoked by uid 99); 20 Aug 2004 15:26:43 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.194.39.81] (HELO flying.sc) (209.194.39.81) by apache.org (qpsmtpd/0.27.1) with SMTP; Fri, 20 Aug 2004 08:26:42 -0700 Received: (qmail 25103 invoked from network); 20 Aug 2004 15:30:18 -0000 Received: from unknown (HELO gulfstream) (wannamak@172.16.3.21) by flying.sc with SMTP; 20 Aug 2004 15:30:18 -0000 From: "Keith Wannamaker" To: "Tomcat Developers List" Subject: RE: Where's 4.1.31? Date: Fri, 20 Aug 2004 11:26:41 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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) In-Reply-To: <9C5166762F311146951505C6790A9CF801FC38F2@US-VS1.corp.mpi.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi Yoav, thanks for the release documentation. Do you mind if I check this in to jt-4.0? I think it would be very helpful. I am aware that 5.0 uses "significantly different code" which is in itself a good reason for continuing maintenance releases of 4.1. Backporting patches would be a nice side-improvement if it were done, but I think there have been enough fixes to 4.1 itself to warrant a new release without said backports. >From a procedural standpoint, it is my understanding that the only vote needed is one to label a rc (ie beta or stable). Is that correct? If so, I'd like to be the 4.1.31 RM and I will go to work on syncing the release notes and get an rc out this weekend. Keith -----Original Message----- From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com] Sent: Friday, August 20, 2004 10:44 AM To: Tomcat Developers List Subject: RE: Where's 4.1.31? Hi, The process is already somewhat documented. For example, http://cvs.apache.org/~yoavs/tomcatReleaseManager.html is my personal notes, and http://jakarta.apache.org/commons/releases/ is mostly Jakarta-general, not specific to Commons. It deviates from the process you posted in that we usually label a release alpha or beta, leave it out in the "wild" for a bit to give users a chance to use it, and then call it stable (with a new announcement). --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org