Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Date: 20 Jan 2001 19:28:21 -0000
Message-ID: <20010120192821.75705.qmail@apache.org>
From: costin@apache.org
To: jakarta-tomcat-cvs@apache.org
Subject: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3

costin      01/01/20 11:28:21

  Modified:    .        RELEASE-PLAN-3.3
  Log:
  Added a paragraph about the release team and release manager, listing
  the current volunteers. ( the final list will be of course decided
  in the voting process ).
  
  Added an action item to add a credits page with the members of the
  release team ( will be part of the standard distribution, so people
  can contact the right persons ).
  
  Revision  Changes    Path
  1.3       +31 -0     jakarta-tomcat/RELEASE-PLAN-3.3
  
  Index: RELEASE-PLAN-3.3
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/RELEASE-PLAN-3.3,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- RELEASE-PLAN-3.3	2001/01/19 03:28:00	1.2
  +++ RELEASE-PLAN-3.3	2001/01/20 19:28:20	1.3
  @@ -42,6 +42,11 @@
   
       5. Improve the test suite.
   
  +    6. Add a "credits.html" ( or similar ) with information about the 
  +       +1 commiters that made the release possible and all the volunteers 
  +       that contribute to it. Given the ammount of responsiblity and
  +       work that is required I think this is an absolute requirement.
  +
   Tomcat 3.3 Milestone 1 Release:
   
   	Code Freeze/Tag Date:	Feb 1, 2001 (?)
  @@ -158,4 +163,30 @@
   The release team must coordinate the maintainace and support of tomcat, 
   dispatching bugs and user requests to developers and acting as the 
   last resort in resolving major support issues. 
  +
  +Release Team
  +============
  +
  +The release team will be composed from the commiters that give the binding
  ++1 on the release plan and release proposal. It must have at least 3
  +memebers, and follow the rules that will be established. 
  +
  +The release team will coordinate the execution of the release plan, dispatch
  +bugs to volunteers, review commits, and act as a lead in the release
  +process.
  +
  +One of the team members will act as "Release Manager" and will be 
  +responsible for building the milestones, making the announcements about
  +the release progress and all other roles that will be set by PMC and 
  +commiters.
  +
  +Larry Isaacs has volunteered as a Release Manager, and Henri Gomez has
  + volunteered to act as a backup and help on the Unix side. So far, 4 people
  +had volunteered to be part of the release team - Ignacio Ortega (Nacho)
  +and Costin Manolache are the other 2. The final team will be determined
  +by the vote that will take place, any commiter voting a binding +1 becoming 
  +a member of the Release Team. It is possible for a team member to retire as
  + long as the minimum of 3 members is maintained, and one of the members agrees
  +to act as Release Manager. 
  +