forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r526678 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Date Mon, 09 Apr 2007 09:05:55 GMT
Author: crossley
Date: Mon Apr  9 02:05:55 2007
New Revision: 526678

URL: http://svn.apache.org/viewvc?view=rev&rev=526678
Log:
Add note to read through these notes often in the lead up to the release.
Perhaps different order of steps is needed.

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=526678&r1=526677&r2=526678
==============================================================================
--- 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 Mon Apr
 9 02:05:55 2007
@@ -67,7 +67,9 @@
 </warning>
             <p>This documents the steps that the Release Manager (RM) should follow
when doing a Forrest release. Note
                 that it might have mistakes - we seem to discover something new each time
and some steps might need to
-                happen in a different order. Fine tune these notes for next time. Do some
practice runs.</p>
+                happen in a different order. Fine tune these notes for next time. Do some
practice runs.
+              Read through these notes often in the lead up to the release to imagine the
effect and order of some steps.
+            </p>
 
             <p>There are some steps that other committers, and even developers, can
assist with, especially in the areas
                 of getting ready for the release and the final testing. Many of the steps
can be done only by the
@@ -246,7 +248,7 @@
                   http://localhost:8888/releaseNotes_&dt;.txt
                 </li>
                 <li>
-                  Prepare the announcement text. Create a file etc/announcement-x.txt
+                  Prepare the announcement text. Create a file admin/announcement-x.txt
                   (by 'svn move' the old one) and list the major new features, e.g. locationmap.
                 </li>
                 <li>
@@ -425,6 +427,12 @@
                 <li>Do any final work, such as license header checks and xml code cleanup.
                 </li>
                 <li>
+                    <p>Ensure that your Java version is the lowest specified of our
supported versions.</p>
+                    <note> Set the environment variable JAVA_HOME to the path of the
Java version. Note for Windows: If
+                        you change the setting in system properties, you need to logout and
login again for the changes
+                        to become effective.</note>
+                </li>
+                <li>
                     <p>Run the following quick tests from the command line of your
system to ensure that all is well:</p>
                     <ul>
                         <li>
@@ -504,12 +512,6 @@
                   Update the etc/RELEASE-NOTES-&d;.txt as described above.
                 </li>
                 <li>Commit all of the above changes.</li>
-                <li>
-                    <p>Set your Java version to be the lowest specified of our supported
versions.</p>
-                    <note> Set the environment variable JAVA_HOME to the path of the
Java version. Note for Windows: If
-                        you change the setting in system properties, you need to logout and
login again for the changes
-                        to become effective.</note>
-                </li>
                 <li>
                     <p>Take note of the SVN revision number of your trunk by running
<code>svn info</code> from the
                         command line in the Release Candidate's root dir and look at the
"Last Changed Rev: ######".



Mime
View raw message