forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r409266 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Date Wed, 24 May 2006 23:58:46 GMT
Author: crossley
Date: Wed May 24 16:58:45 2006
New Revision: 409266

Add warning that doc is still being developed.
Clarify why we temporarily leave the previous dist in place.
Clarify what happens at beginning of code freeze.


Modified: forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
--- 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 May
24 16:58:45 2006
@@ -27,6 +27,10 @@
         <section id="About">
             <title>About this Document</title>
+This document is still being developed from etc/RELEASE_PROCESS.txt and
+some steps will need to be re-arranged.
             <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>
@@ -272,8 +276,12 @@
                     <p> Rename the deployed plugins directory by issuing the following
commands at the command line </p>
-                    <source> cd /svn/asf/forrest-site svn up svn mv plugins/0.8-dev
plugins/0.8 svn mkdir
-                        plugins/0.9-dev svn commit</source>
+                    <source>cd /svn/asf/forrest-site
+svn update
+svn mv plugins/0.8-dev plugins/0.8
+svn mkdir plugins/0.9-dev
+svn status
+svn commit</source>
                     <fixme author="fso">Issue them where and to what end?</fixme>
@@ -287,12 +295,11 @@
             <note>You can practice the following steps (as far as creating the branch)
without committing anything even
                 before code-freeze. This ensures a good release candidate.</note>
-                <li>Use template <a href="anounce_code_freeze.txt">anounce_code_freeze.txt</a>
to send a reminder-mail
-                    to dev-list when the code-freeze commences.</li>
+                <li>Use template <a href="anounce_code_freeze.txt">anounce_code_freeze.txt</a>
to send email
+                    to dev-list that the code-freeze has now commenced.</li>
                     <p>Update your release checkout (svn up) to include last minute
-                <li> </li>
                     <p>Run the following quick tests from the command line of your
system to ensure that all is well:</p>
@@ -545,7 +552,9 @@
                             ></a> and
-                    <p>Leave the previous dist there as well, until after the announcement.</p>
+                    <p>Leave the previous dist there as well as the new one, until
after the announcement
+                    (because mirrors.html cannot be updated until most mirrors have received
the release).
+                    </p>
                     <note>The other files there (HEAD.html README.html LICENSE.txt
KEYS) are all automatically updated
                         from the SVN:forrest/dist/ repository. </note>
@@ -623,7 +632,7 @@
     around line 52:
     |                 Forrest Site Builder                  |
-    |                        0.8-dev                             |
+    |                        0.8-dev                        |
                 <li><p>Remove old dist files from the /www/

View raw message