remm        02/04/25 01:59:51

  Modified:    .        RELEASE-PLAN-4.1.txt
  Log:
  - Update status.
  - Update with "new" build numbering scheme.
  
  Revision  Changes    Path
  1.5       +9 -9      jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt
  
  Index: RELEASE-PLAN-4.1.txt
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- RELEASE-PLAN-4.1.txt      24 Apr 2002 11:59:03 -0000      1.4
  +++ RELEASE-PLAN-4.1.txt      25 Apr 2002 08:59:51 -0000      1.5
  @@ -1,4 +1,4 @@
  -$Id: RELEASE-PLAN-4.1.txt,v 1.4 2002/04/24 11:59:03 remm Exp $
  +$Id: RELEASE-PLAN-4.1.txt,v 1.5 2002/04/25 08:59:51 remm Exp $
   
                         Release Plan for Apache Tomcat 4.1
                         ==================================
  @@ -28,18 +28,19 @@
     from build.xml scripts.
   * Many other miscanellous improvements
   
  -This Release Plan proposes the following schedule:
  -
  -  Friday, April 26, 2002          Apache Tomcat 4.1 Beta 1
  +Apache Tomcat 4.1 will use the build numbering and release process first used 
  +in the Apache HTTPd 2.0.x project.
  +Milestone builds, numbered 4.1.x, will be released as needed and will 
  +recieve a stability rating after a one week testing period. The rating can be
  +either: Alpha, Beta, or Stable.
   
  -  Friday, May 10, 2002            Apache Tomcat 4.1 Beta 2
  +This Release Plan proposes the following schedule:
   
  -  Friday, May 17, 2002            Apache Tomcat 4.1 Release Candidate
  +  Friday, April 26, 2002          Apache Tomcat 4.1.0
   
   In order to complete final release, all outstanding Bugzilla bug reports
   against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for 
  -later releases.  After the first 4.1 Release Candidate, other RC releases may
  -be made as needed until one is promoted as Final by the Tomcat committers.
  +later releases.
   
   This Release Plan proposes the following classification of current outstanding
   bug reports in the bug tracking system, sorted by component and their ID
  @@ -78,7 +79,6 @@
   5585 Error page not displayed
   5666 Implicit object _value on jsp pages
   5793 variable element in tld with TagExtraInfo class
  -5903 version attribute in <jsp:root>
   6196 <jsp:forward> should trigger IllegalStateException when buffer flushed
   6908 JavaCompiler interface setOutputDir always called with null parameter
   7007 Invalid names in web.xml generated by JspC for top-level JSP pages
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to