Return-Path: 
 <commons-dev-return-28189-qmlist-jakarta-archive-commons-dev=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@apache.org
Received: (qmail 53448 invoked from network); 25 Apr 2003 10:26:27 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 25 Apr 2003 10:26:27 -0000
Received: (qmail 12798 invoked by uid 97); 25 Apr 2003 10:28:37 -0000
Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org
Received: (qmail 12791 invoked from network); 25 Apr 2003 10:28:37 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 25 Apr 2003 10:28:37 -0000
Received: (qmail 53248 invoked by uid 500); 25 Apr 2003 10:26:25 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 53233 invoked by uid 500); 25 Apr 2003 10:26:25 -0000
Received: (qmail 53228 invoked from network); 25 Apr 2003 10:26:25 -0000
Received: from icarus.apache.org (208.185.179.13)
  by daedalus.apache.org with SMTP; 25 Apr 2003 10:26:25 -0000
Received: (qmail 23823 invoked by uid 1289); 25 Apr 2003 10:26:24 -0000
Date: 25 Apr 2003 10:26:24 -0000
Message-ID: <20030425102624.23822.qmail@icarus.apache.org>
From: rdonkin@apache.org
To: jakarta-commons-cvs@apache.org
Subject: cvs commit: jakarta-commons/docs/releases prepare.html release.html
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

rdonkin     2003/04/25 03:26:23

  Modified:    docs/releases prepare.html release.html
  Log:
  Improved release documents
  
  Revision  Changes    Path
  1.5       +27 -2     jakarta-commons/docs/releases/prepare.html
  
  Index: prepare.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/docs/releases/prepare.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- prepare.html	7 Apr 2003 09:05:06 -0000	1.4
  +++ prepare.html	25 Apr 2003 10:26:23 -0000	1.5
  @@ -207,6 +207,27 @@
       The <code>example text</code> consistently assumes that preparation are being made to release 
       version <em>1.2</em> of component <em>foo</em>.
       </p>
  +                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
  +      <tr><td bgcolor="#828DA6">
  +        <font color="#ffffff" face="arial,helvetica,sanserif">
  +          <a name="Consider A Release Branch"><strong>Consider A Release Branch</strong></a>
  +        </font>
  +      </td></tr>
  +      <tr><td>
  +        <blockquote>
  +                                    <p>
  +Consider whether a release branch is needed. This is judgement call. A release branch increases the
  +complexity of the release but can help to prevent misunderstandings. Usually, for a small component 
  +only good communication is needed. 
  +            </p>
  +                                                <p>
  +These documents assume a release from <code>CVS HEAD</code>. Some small modification to the procedure
  +may be needed when using a release branch.
  +            </p>
  +                            </blockquote>
  +      </td></tr>
  +      <tr><td><br/></td></tr>
  +    </table>
                               </blockquote>
           </p>
         </td></tr>
  @@ -289,6 +310,10 @@
           Go through the CVS logs for all source files which have changed since the last version.
           Analyse the log messages. Enhancements and new features need to be collated by topic.
           Bugs fixed should be listed separately together with a short summary of the bug.
  +        A little time may be saved by checking the logs only for the source files.
  +        </p>
  +                                                <p>
  +Please remember to spell check the release notes. Please break lines at 80 characters.
           </p>
                               </blockquote>
         </td></tr>
  @@ -365,7 +390,7 @@
           </p>
                                                   <p>
           Now tag (for example <code>FOO_1_2_RC1</code>) and build distributions from that tag 
  -        (as per full release). For commons components, it's usually unnecessary to post the 
  +        (as <a href="release.html">per full release</a>). For commons components, it's usually unnecessary to post the 
           release candidate on the main release site. (It's usually good enough to upload it 
           into the public folder <em>~/public_html</em> in your home directory 
           on <code>cvs.apache.org</code>.)
  @@ -409,7 +434,7 @@
           <blockquote>
                                       <p>
           Once the vote has succeeded, then post a <code>[RESULT][VOTE] Release foo 1.0</code> email to 
  -        <strong>commmons-dev@jakarta.apache.org</strong> and cc <strong>pmc@jakarta.apache.org</strong>.
  +        <strong>commons-dev@jakarta.apache.org</strong> and cc <strong>pmc@jakarta.apache.org</strong>.
           </p>
                                                   <p>
           Tag the release now. (This will ensure that there are no problems with badly timed commits.)
  
  
  
  1.6       +1 -1      jakarta-commons/docs/releases/release.html
  
  Index: release.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/docs/releases/release.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- release.html	15 Apr 2003 11:49:19 -0000	1.5
  +++ release.html	25 Apr 2003 10:26:23 -0000	1.6
  @@ -833,7 +833,7 @@
                                                   <p>
   Please remember to give a brief description of you component. Please also remember to remind people 
   about verifying the signatures. The subject should be something like <code>[ANNOUNCEMENT] Foo 1.2 Released</code>. 
  -You might like to send this mail from your apache account. Please spell check the document!
  +Send this mail from your apache account. Please spell check the document!
   </p>
                                                   <p>
   This should go to (at least) the following mailing lists:
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org