The Apache Project

Objective

$Id: release-plan_1_2_0.xml 51697 2004-08-31 17:23:10Z jmitchell $

The objective of the Struts 1.2.0 release is to provide an official version of all the changes that have been made to the main trunk of the jakarta-struts CVS since the release of Struts 1.1 Final.

The Plan

Since the release of version Struts 1.1 Final, we have removed many of the elements deprecated between Struts 1.0 and Struts 1.1 and made several bug fixes and nominal enhancements.

The following release plan is proposed for Struts 1.2.0:

  • Tag Date - Saturday, February 21, 2004, 23:59:59
  • Release Manager(s) - Ted Husted, Martin Cooper
  • Alpha Release Announcement - To the following mailing list:
    • struts-dev@jakarta.apache.org
  • Beta/General Release Announcement - To the following mailing lists:
    • struts-dev@jakarta.apache.org
    • struts-user@jakarta.apache.org
    • announcements@jakarta.apache.org

The release process shall follow the same general procedures established for the Apache HTTPD project and Jakarta Commons products, and utilize the HTTPD numbering scheme.

The release will initially be given an Alpha status and made available through the Release Manager's home directory. Pursuant to a Majority Vote on the struts-dev Mailing List, the release may be moved to the public release directory. The vote may also serve to reclassify the release to be of Beta or General Availability (GA) quality, as defined by the Apache HTTPD project. Subsequent votes may reclassify the release, either to promote it or to demote it, as need be.

Specific Release Criteria

Prior to the Struts 1.2.0 release, these specific action items must be completed:

  • The Roadmap page must be updated with an explanation of the new release numbering scheme.

Standard Release Criteria

Prior to any release by the Struts Committers, including this one, the following action items must be completed:

  • Resolve showstoppers. Relevant Bugzilla tickets verified by a Struts Committer to have the Severity BLOCKER, CRITICAL, or MAJOR must be "Resolved" with one of these Bugzilla resolutions: FIXED, INVALID, WONTFIX, WORKSFORME.
  • Test example applications. All example applications included with the release shall operate successfully under the Reference Implementation containers for the Servlet/JSP specifications supported by the release. In the case of a Struts 1.x.x release, these containers are:
    • Tomcat 3.3 (Servlet/JSP 2.2/1.1 Reference Implementation)
    • Tomcat 4.1 (Servlet/JSP 2.3/1.2 Reference Implementation)
    The best available version of each container shall be used, as documented by the Tomcat website at the time the test is conducted.
  • Update Release Notes. The Release Notes for the distribution shall be updated to summarize any substantial changes and improvements since the prior release, including updates to bundled documentation and example applications.

Minor Release Criteria

Prior to an initial Struts minor release (#.#.0), the following action items must be completed:

  • Review pending issues. All relevant Bugzilla reports marked "Resolved" with the Resolutions LATER or REMIND shall be reviewed to ensure that pending issues have been addressed prior to the release.
  • Review pending enhancements. All relevant Bugzilla reports marked "Enhancement" shall be reviewed by the Release Manager to ensure that all suitable enhancements have been made prior to the release.
  • Resolve new issues. All relevant Bugzilla tickets MUST be marked as "Enhancement" or "Resolved" with any of the legal Bugzilla resolutions (FIXED, INVALID, WONTFIX, LATER, REMIND, WORKSFORME).
    • Bug reports that are resolved as LATER or REMIND will include comments as to whether those specific issues will be dealt with in a forthcoming minor release or whether they will be considered in a future major release.
  • A Majority Vote shall take place on the struts-dev mailing list to approve a release plan for the initial minor release.