$Id: release-plan-1.1rc1.xml,v 1.1 2003/02/16 05:35:54 martinc Exp $

The objective of the Struts 1.1 Release Candidate 1 release is to create a milestone release in preparation for an imminent Struts 1.1 Final release. As a release candidate, this milestone release currently contains no known showstoppers.

A number of bugs have been fixed since the third Beta release of Struts 1.1, and all remaining bugs have been categorized either as enhancements, or as problems which can be fixed in a release subsequent to Struts 1.1 Final. Therefore it is time to make the latest code base available as a first Release Candidate. The goal is to move towards a final Struts 1.1 release as soon as is practicable.

Therefore, the following release plan is proposed for Struts 1.1 Release Candidate 1:

• Code Freeze / Tag Date - Tuesday, February 18, 2003, 23:59:59
• Release Manager - Martin Cooper
• Release Announcement - To the following mailing lists:
  • announcements@jakarta.apache.org
  • struts-dev@jakarta.apache.org
  • struts-user@jakarta.apache.org

Prior to the release of Struts 1.1 Release Candidate 1, the following action items must be completed:

• The Struts 1.1 Release Notes document shall be updated to describe substantial changes and improvements since the Struts 1.0.2 release, along with associated updates to the main Struts Documentation Application pages describing the new release.
• All of the Struts example applications that are included with the release shall operate successfully in the following servlet containers:
  • Tomcat 3.3.1
  • Tomcat 4.0.6
  • Tomcat 4.1.18
• A release vote shall take place on the STRUTS-DEV mailing list to approve this plan. The release vote MUST pass by "Majority Approval" of Struts committers.

Prior to the release of a subsequent Struts 1.1 Final release, the following action items must be completed:

• All Bugzilla bug reports against Struts 1.1 nightly builds MUST be marked as "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 subsequent beta, release candidate, or final release, or whether they will be scheduled for consideration in a subsequent release time frame.