Attached is a draft of the 2.1.1 release plan.  I cribbed the formatting
from Struts, hope they don't mind.


Matt Bishop
[EMAIL PROTECTED]


"We are all here on earth to help others.  What I can't figure out is what
the others are here for."
    - W. H. Auden

<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>James Release Plan (Version 2.1.1)</title>
</head>
<body vlink="#023264" 
alink="#023264" link="#023264" text="#000000" bgcolor="#ffffff">
<tr>
  <td 
colspan="2"><a href="http://jakarta.apache.org";><img border="0" align="left" 
src="../images/jakarta-logo.gif"></a><a href="http://jakarta.apache.org/james";><img 
border="0" align="right" src="images/james-logo.jpg"></a></td>
</tr>
<tr>
  <td 
colspan="2"><hr>
  </td>
</tr>
<tr>
  <td valign="top" width="120"> </td>
  <td 
valign="top"> <a name="Objective"></a>
    <table width="100%" cellpadding="5" 
cellspacing="5" border="0">
      <tr>
        <td bgcolor="#023264"><font size="+1" 
face="arial,helvetica,sanserif" color="#ffffff"><strong>Objective</strong></font></td>
      </tr>
      <tr>
        <td><blockquote>
            <p>The objective of the 
<strong>James 2.1.1</strong> release is to stabilize the 2.1 release. Several known 
issues will be addressed
              in addition to issues that are yet to be 
discovered by the user
              community. This plan will be updated as these 
issues are discovered.<br>
            </p>
          </blockquote>
        </td>
     
 </tr>
    </table>
    <a name="Plan"></a>
    <table width="100%" cellpadding="5" 
cellspacing="5" border="0">
      <tr>
        <td bgcolor="#023264"><font size="+1" 
face="arial,helvetica,sanserif" color="#ffffff"><strong>The Plan</strong></font></td>
 
     </tr>
      <tr>
        <td><blockquote>
            <p>A number of new features 
have been added to James in the 2.1 release, including...(TODO:
              what's 
new in James 2.1?)</p>
            <p>No new Features will be added to James.</p>
     
       <p>Testing effort will be focused on testing the new features in James, 
regressing
              previously-closed bugs, and expanding the client and server 
configuration
              test coverage as much as possible. The following test plan 
(TODO:
              write a test plan :) )</p>
            <p>Reported bugs must be 
CLOSED by someone other than the person fixing the bug,
              preferrably the 
person that filed the bug. All bugs that are to
              be resolved WORKSFORME, 
WONTFIX, and LATER must be resolved as
              such by someone other than the 
person initially assigned to the
              bug.</p>
            <p>Coding effort 
will be focused on driving the bug count to the release criteria
              bug 
profile and maintaining this profile for 30 days. All changes
              to the 
code base must be traced to a bug number.</p>
            <p>Therefore, the following 
release plan is proposed for James 2.1.1: <br>
            </p>
            <ul>
      
        <li><em>Code Freeze / Tag Date</em> - TBD</li>
              <li><em>Release 
Manager</em> - TBD</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>
          </blockquote>
        </td>
      </tr>
    </table>
    <a 
name="Criteria"></a>
    <table width="100%" cellpadding="5" cellspacing="5" 
border="0">
      <tr>
        <td bgcolor="#023264"><font size="+1" 
face="arial,helvetica,sanserif" color="#ffffff"><strong>Release 
Criteria</strong></font></td>
      </tr>
      <tr>
        <td><blockquote>
         
   <p>Prior to the release of James 2.1.1, the following action items must be 
completed:<br>
            </p>
            <ul>
              <li>The James 2.1.1 
Release Notes document shall be updated to describe all bugs
                fixed and 
other improvements since the James 2.1 release, along
                with associated 
updates to
                the main James documentation pages describing
              
  the new release.</li>
              <li>All of the James Build Verification Tests 
(in the tests directory) and example
                applications that are included 
with the release shall operate
                successfully in the following 
configurations:
                <ul>
                  <li>Windows 2000:
              
      <ul>
                      <li>JDK 1.2.2_014 (or whatever the latest version is 
near release)</li>
                      <li>JDK 1.3.1_06 (latest)</li>
               
       <li>JDK 1.4.1_01 (latest)</li>
                    </ul>
                  
</li>
                  <li>Red Hat Linux 7.2
                    <ul>
                
      <li>JDK 1.2.2_014 (or whatever the latest version is near release)</li>
         
             <li>JDK 1.3.1_06 (latest)</li>
                      <li>JDK 1.4.1_01 
(latest)</li>
                    </ul>
                  </li>
                  
<li>Mac OS X 10.2, JDK 1.3.1</li>
                  <li>Any others?Do we need to test 
on NT4, XP, Win98?</li>
                </ul>
              </li>
              
<li>All <a href="http://nagoya.apache.org/bugzilla/";>Bugzilla</a> bug reports against 
James 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>
              
<li>Once the bug profile has been accomplished for 30 days, a release vote shall
      
          take place on the JAMES-DEV mailing list to approve this plan.
              
  The release vote MUST pass by "Majority Approval" of James committers.</li>
         
   </ul>
          </blockquote>
        </td>
      </tr>
    </table>
</body>
</html>
--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to