Struts Release Plan (Version 1.1b1)
Struts
Welcome
Objective
$Id: release-plan-1.1b1.xml 51317 2004-01-06 05:49:41Z rleland $
The objective of the Struts 1.1 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.1 Final
release is created.
The Plan
Many new features have been added to the nightly builds since the release
of Struts 1.0, and many bugs have been fixed. Several of the new features are
in high demand by current Struts users, and so it is time to start the process
of making this new code base available as a formal release. The first step in
this process is an initial beta release, with the goal of moving towards a
release candidate and then a final Struts 1.1 release as
soon as is practicable.
Therefore, the following release plan is proposed for Struts 1.1 Beta 1:
Code Freeze / Tag Date - Monday, March 18, 2002
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
Release Criteria
Prior to the release of Struts 1.1 Beta 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
Tomcat 4.0.3
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 release candidate, 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
release candidate, or final release, or whether they will be scheduled
for consideration in a subsequent release time frame.
Copyright (c) 2000-2005, The Apache Software Foundation -
Comments?
