The Apache Project

Objective

$Id: release-plan-1.0b1.xml 51063 2003-09-09 17:49:23Z sraeburn $

The objective of the Struts 1.0-beta-1 release is to create a milestone release against which a final series of bug fixes and documentation updates can occur before a Struts 1.0 Final release is created.

The Plan

The code base for Struts has been in an informal "feature freeze" for several weeks, while development focus has been on bug fixes and the completion of required documentation. Both of these goals have been substantially achieved, so it is time for a formal beta release - with the goal of moving quickly to a final Struts 1.0 release shortly thereafter, if no disabling defects are found.

Therefore, the following release plan is proposed for Struts 1.0-beta-1:

  • Code Freeze / Tag Date - Wednesday, February 21, 2001
  • Release Manager - Craig McClanahan
  • Release Announcement - To the following mailing lists and web sites:
    • ANNOUNCEMENTS@JAKARTA.APACHE.ORG
    • GENERAL@JAKARTA.APACHE.ORG
    • STRUTS-DEV@JAKARTA.APACHE.ORG
    • STRUTS-USER@JAKARTA.APACHE.ORG
    • JSP-INTEREST@JAVA.SUN.COM
    • SERVLET-INTEREST@JAVA.SUN.COM
    • http://www.freshmeat.net

Release Criteria

Prior to the release of Struts 1.0-beta-1, the following action items must be completed:

  • All Bugzilla bug reports against Struts 1.0 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 1.0 beta or final release, or whether they will be scheduled for consideration in a subsequent release time frame.
  • Any remaining items on the Struts 1.0 TODO list shall be completed.
  • The Struts 1.0 Release Notes document shall be updated to describe substantial changes and improvements since the Struts 0.5 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:
  • 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.