martinc 02/03/09 22:22:40
Modified: doc project.xml
Added: doc/proposals release-plan-1.1b1.xml
Log:
Added release plan for Struts 1.1 Beta 1.
Revision Changes Path
1.20 +2 -0 jakarta-struts/doc/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/project.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- project.xml 20 Feb 2002 00:42:49 -0000 1.19
+++ project.xml 10 Mar 2002 06:22:40 -0000 1.20
@@ -44,6 +44,8 @@
href="proposals/workflow.html"/>
<item name="Wish List"
href="proposals/todo-1.1.html"/>
+ <item name="Struts 1.1 Beta 1 Release Plan"
+ href="proposals/release-plan-1.1b1.html"/>
</menu>
</project>
1.1 jakarta-struts/doc/proposals/release-plan-1.1b1.xml
Index: release-plan-1.1b1.xml
===================================================================
<?xml version="1.0"?>
<document url="./release-plan-1.1b1.xml">
<properties>
<author>Martin F N Cooper</author>
<title>Struts Release Plan (Version 1.1b1)</title>
</properties>
<body>
<section name="Objective" href="Objective">
<p><font size="-2">$Id: release-plan-1.1b1.xml,v 1.1 2002/03/10 06:22:40 martinc
Exp $</font></p>
<p>The objective of the <strong>Struts 1.1 Beta 1</strong> release is to
create a milestone release against which a final series of bug fixes and
documentation updates can occur before a <strong>Struts 1.1 Final</strong>
release is created.</p>
</section>
<section name="The Plan" href="Plan">
<p>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 <strong>Struts 1.1</strong> release as
soon as is practicable.</p>
<p>Therefore, the following release plan is proposed for Struts 1.1 Beta 1:
</p>
<ul>
<li><em>Code Freeze / Tag Date</em> - Tuesday, March 12, 2002</li>
<li><em>Release Manager</em> - Martin Cooper</li>
<li><em>Release Announcement</em> - To the following mailing lists:
<ul>
<li>[EMAIL PROTECTED]</li>
<li>[EMAIL PROTECTED]</li>
<li>[EMAIL PROTECTED]</li>
</ul></li>
</ul>
</section>
<section name="Release Criteria" href="Criteria">
<p>Prior to the release of Struts 1.1 Beta 1, the following action items
must be completed:</p>
<ul>
<li>All <a href="http://nagoya.apache.org/bugzilla/";>Bugzilla</a> 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).</li>
<li>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.1 beta, release candidate, or final release, or whether they will be
scheduled for consideration in a subsequent release time frame.</li>
<li>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.</li>
<li>All of the Struts example applications that are included with the release
shall operate successfully in the following servlet containers:
<ul>
<li><a href="http://jakarta.apache.org/tomcat";>Tomcat 3.3</a></li>
<li><a href="http://jakarta.apache.org/tomcat";>Tomcat 4.0.3</a></li>
</ul></li>
<li>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.</li>
</ul>
</section>
</body>
</document>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
