forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r530216 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Date Thu, 19 Apr 2007 01:18:17 GMT
Author: crossley
Date: Wed Apr 18 18:18:16 2007
New Revision: 530216

URL: http://svn.apache.org/viewvc?view=rev&rev=530216
Log:
Warn about the time and energy required.
Add more notes for RM preparation.

Modified:
    forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml

Modified: forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml?view=diff&rev=530216&r1=530215&r2=530216
==============================================================================
--- forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml (original)
+++ forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml Wed Apr
18 18:18:16 2007
@@ -34,7 +34,7 @@
 <!ENTITY rdate '2007-04-16'>
 ]>
 <!-- The entities above are for the current state,
-  i.e. preparing for the upcoming release:
+  i.e. preparing for the upcoming release (using 0.8 as the example):
   &c;  = current release version, e.g. 0.7
   &cd; = current release version docs, e.g. docs_0_70
   &cs; = current release version site URI, e.g. 0.70 (as in site:v0.70)
@@ -63,9 +63,10 @@
     <section id="About">
       <title>About this document</title>
       <warning>
-        This document is still being developed and some steps might need to be
-        re-arranged. There are some fixme notes that we will review after this
-        release.
+        This document is constantly being developed and some steps will need to be
+        re-arranged. There are some fixme notes that we will review after each
+        release. Do not take this document at face value - always try to visualise the
+        effect of each step.
       </warning>
       <p>
         This documents the steps that the Release Manager (RM) should follow
@@ -81,6 +82,10 @@
         and the final testing. Many of the steps can be done only by the Release
         Manager.
       </p>
+      <p>
+        The lead-up to the release is a good opportunity to build the project community
+        and to draw in new developers. The steps in this process try to maximise that.
+      </p>
     </section>
     <section id="rm">
       <title>Who is the Release Manager</title>
@@ -108,9 +113,18 @@
         assistant would probably hinder.
       </p>
       <p>
+        The RM needs to have an incredible amount of time and energy available,
+        especially to prepare the first release candidate and to finalise the release.
+      </p>
+      <p>
         The RM should be comfortable with using SVN and be familiar with the ASF
         hardware, with the distribution mirror system, and with ASF release
-        procedures. The following notes are terse. If you don't understand, then
+        procedures. Also need to be a quick decision-maker and able to find and solve
+        issues on the spot. It would be nice if others help to solve last minute
+        issues, but don't expect it.
+      </p>
+      <p>
+        The following notes are terse. If you don't understand, then
         probably not ready to be RM.
       </p>
     </section>
@@ -206,7 +220,7 @@
         familiar with standard procedures and Apache terminology. This is
         crucial for a successful release.
       </p>
-      <ol>
+      <ul>
         <li><p>
             If you have never done a release before or need to refresh your
             memory, read all about Apache releases in general at
@@ -214,16 +228,18 @@
             (note that these documents change often). Make sure any assistants
             have read and understood this as well.
           </p></li>
+        <li>As discussed above, be sure that you have plenty of time and energy.
+          You will need to be persistent throughout the process.
+        </li>
         <li><p>
-            Be familiar with the process of signing releases and generating MD5
+            Be familiar with the process of signing release packages and generating MD5
             and PGP. Some more info is at
-            <a
-                            href="http://www.apache.org/dev/release-signing.html">Signing
-            Releases</a> and
-            <a
-                            href="http://forrest.apache.org/mirrors.cgi#verify"
-                            >http://forrest.apache.org/mirrors.cgi#verify</a>
+            <a href="http://www.apache.org/dev/release-signing.html">Signing
+            Releases</a> and our download notes for the 
+            <a href="http://forrest.apache.org/mirrors.cgi#verify">Verification</a>.
           </p></li>
+        <li>Practice signing email in readiness for the announcment.</li>
+        <li>Investigate the release procedure notes of other ASF projects.</li>
         <li>
                   Make sure that the network connection is reliable and efficient.
                 </li>
@@ -232,7 +248,9 @@
             release. Do this well ahead of time to avoid delays, and ensure that
             Forrest works for you.
           </p></li>
-      </ol>
+        <li>Get a printout of this document to scribble notes as you go.</li>
+        <li>Use a text file to prepare/record your svn merge commands.</li>
+      </ul>
     </section>
     <section id="PrepRelPlan">
       <title>Preparing the Release Plan</title>



Mime
View raw message