Return-Path: <marcsaeg@apache.org>
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 75002 invoked by uid 500); 8 Feb 2001 01:05:59 -0000
Delivered-To: apmail-jakarta-tomcat-cvs@apache.org
Received: (qmail 74916 invoked by uid 1225); 8 Feb 2001 01:05:38 -0000
Date: 8 Feb 2001 01:05:38 -0000
Message-ID: <20010208010538.74907.qmail@apache.org>
From: marcsaeg@apache.org
To: jakarta-tomcat-cvs@apache.org
Subject: cvs commit: jakarta-tomcat RELEASE-PLAN-3.2.2

marcsaeg    01/02/07 17:05:35

  Modified:    .        Tag: tomcat_32 RELEASE-PLAN-3.2.2
  Log:
  Updated release criteria to include Bugzilla resolution requirements.
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.2   +8 -6      jakarta-tomcat/Attic/RELEASE-PLAN-3.2.2
  
  Index: RELEASE-PLAN-3.2.2
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/Attic/RELEASE-PLAN-3.2.2,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- RELEASE-PLAN-3.2.2	2001/02/07 23:24:53	1.1.2.1
  +++ RELEASE-PLAN-3.2.2	2001/02/08 01:05:27	1.1.2.2
  @@ -1,4 +1,4 @@
  -$Id: RELEASE-PLAN-3.2.2,v 1.1.2.1 2001/02/07 23:24:53 marcsaeg Exp $
  +$Id: RELEASE-PLAN-3.2.2,v 1.1.2.2 2001/02/08 01:05:27 marcsaeg Exp $
   
   NOTE:  This document is the first cut at a release plan for the next
          dot release of Tomcat.  Nothing in this document should be
  @@ -52,11 +52,13 @@
   
   Release Criteria:
       
  -    Any bug introduced after Tomcat 3.2.1 MUST be fixed.  Bugs that existed 
  -    prior to the release of Tomcat 3.2.1 that are not fixed before the 
  -    code freeze/beta release will not be fixed in Tomcat 3.2.2.  Once 
  -    Tomcat 3.2.2 is finalized the tomcat_32 branch will be unfrozen and 
  -    developers may commit fixes for a future release.
  +    Any bug introduced by a code change since Tomcat 3.2.1 was released MUST
  +    be fixed.  If it worked in 3.2.1 it will work in 3.2.2.
  +
  +    All Bugzilla items opened against "Tocmat 3" must be marked as RESOLVED.
  +    Those items that are not going to be fixed in Tomcat 3.2.2 will be given
  +    a resolution of LATER.  After Tomcat 3.2.2 is released items marked LATER
  +    will be re-opened and may then be addressed in a future release.
   
       The Tomcat 3.2.2 release MUST run the jakarta-watchdog test suite with no 
       errors on the following platforms:  Linux, Solaris, Windows 9x,