<?xml version="1.0"?>
<document url="./release-plan-1.1-b2.xml">

  <properties>
    <author>Martin F N Cooper</author>
    <title>Struts Release Plan (Version 1.1-b2)</title>
  </properties>

  <body>


  <section name="Objective" href="Objective">

  <p>$Id: release-plan-1.1b2.xml,v 1.4 2004/01/06 05:49:41 rleland Exp $</p>

  <p>The objective of the <strong>Struts 1.1 Beta 2</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>A number of new features have been added to the nightly builds since the
  first Beta release of Struts 1.1, and many bugs have been fixed. It is time,
  therefore, to take the next step in the release process, and make the latest
  code base available as a second Beta release. The goal is to move 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 2:
  </p>
  <ul>
  <li><em>Code Freeze / Tag Date</em> - Saturday, August 10, 2002</li>
  <li><em>Release Manager</em> - Martin Cooper</li>
  <li><em>Release Announcement</em> - To the following mailing lists:
      <ul>
      <li>announcements@jakarta.apache.org</li>
      <li>struts-dev@jakarta.apache.org</li>
      <li>struts-user@jakarta.apache.org</li>
      </ul></li>
  </ul>

  </section>


  <section name="Release Criteria" href="Criteria">

  <p>Prior to the release of Struts 1.1 Beta 2, the following action items
  must be completed:</p>
  <ul>
  <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.1</a></li>
      <li><a href="http://jakarta.apache.org/tomcat">Tomcat 4.0.4</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>

  <p>Prior to the release of a subsequent Struts 1.1 release candidate, the
  following action items must be completed:</p>
  <ul>
  <li>All <a href="http://issues.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
      beta, release candidate, or final release, or whether they will be
      scheduled for consideration in a subsequent release time frame.</li>
  </ul>

  </section>


  <section name="Bugs To Be Addressed" href="Bugs">

  <p>The following bugs must be addressed before Final Release of Struts 1.1.</p>

  <table class="noborder">
    <tr>
      <td colspan="2"><strong>Custom Tags</strong></td>
    </tr>
    <tr>
      <td>1586</td>
      <td>The &lt;html:form&gt; tag generates incorrect focus javascript for radio buttons.</td>
    </tr>
    <tr>
      <td colspan="2"><strong>Documentation</strong></td>
    </tr>
    <tr>
      <td>10537</td>
      <td>[:TODO:] sections (18)</td>
    </tr>
    <tr>
      <td colspan="2"><strong>Example Webapps</strong></td>
    </tr>
    <tr>
      <td>10955</td>
      <td>Error running struts-blank applicaiton under JRun 3.1</td>
    </tr>
    <tr>
      <td colspan="2"><strong>Validator Framework</strong></td>
    </tr>
    <tr>
      <td>7353</td>
      <td>Validator JavaScript Select Error</td>
    </tr>
    <tr>
      <td>10191</td>
      <td>Validator range checking bug</td>
    </tr>
    <tr>
      <td>10348</td>
      <td>Validator is not available under module</td>
    </tr>
    <tr>
      <td>10349</td>
      <td>Validator: date validation does not allow blank input?</td>
    </tr>
    <tr>
      <td>10432</td>
      <td>DynaValidatorActionForm does not validate data</td>
    </tr>
    <tr>
      <td>10584</td>
      <td>Not all validation files are read in Validation PlugIn</td>
    </tr>
  </table>

  </section>


  </body>

</document>
