svn commit: r522177 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml

[cr...@apache.org]

Author: crossley
Date: Sun Mar 25 01:32:39 2007
New Revision: 522177

URL: http://svn.apache.org/viewvc?view=rev&rev=522177
Log:
Note that "code freeze" is defined in the email template.

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=522177&r1=522176&r2=522177
==============================================================================
--- 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 Sun Mar 25 01:32:39 2007
@@ -344,7 +344,7 @@
                 <li>Announce that the code-freeze has now commenced.
                   Use the template <a href="announce_code_freeze.txt">announce_code_freeze.txt</a>
                   to send email to dev-list.
-                  <fixme author="">Define what we mean by "code-freeze".</fixme>
+                  The meaning of "code-freeze" is defined in that template.
                 </li>
                 <li>
                     <p>Update your SVN working copy to include any last minute changes.</p>
@@ -506,7 +506,7 @@
             </ol>
         </section>
 
-        <section>
+        <section id="vote">
             <title>Testing the release candidate and voting</title>
             <p>Get Forrest developers to test the actual distribution on various platforms.</p>
             <ol>
@@ -522,9 +522,9 @@
                       This is especially important if there has been more than one release candidate.</p>
                 </li>
                 <li>
-                    <p>As the votes come in:</p>
+                    <p>During this testing phase, then Release Manager should:</p>
                     <ul>
-                        <li>Make sure the distributions unpack on different systems without problems.</li>
+                        <li>Make sure that people are reporting that the distributions unpack on different systems without problems.</li>
                         <li>Make sure that people have followed the actual user instructions in the Forrest
                             distribution at README.txt and index.html</li>
                         <li>Encourage people to build some difficult sites.</li>
@@ -551,10 +551,12 @@
             <ol>
                 <li>
                     <p>If there have been changes to the trunk since the branch was created, then merge trunk to branch.</p>
+
                     <fixme author="fso">What is the purpose of this step? It doesn't seem to be right because trunk may
                         already contain parts of the next version. What we should do is do all fixing of RC-problems in
                         the rc-branch (same as changing docs) then, on release, merge branch back into trunk to
                         integrate fixes and doc-changes back into trunk. wdyt?</fixme>
+                    <fixme author="dc">It should not contain new functionality because we are in a code freeze</fixme>
                 </li>
                 <li>
                     <p>Tag SVN by doing:</p>
@@ -578,8 +580,8 @@
                         041, 05).</p>
                 </li>
                 <li>
-                    <p>Announce the end of the code-freeze by sendung the email-template <a
-                            href="announce_end_of_code_freeze.txt">announce_end_of_code_freeze.txt</a>to the dev
+                    <p>Announce the end of the code-freeze by sending the email-template <a
+                            href="announce_end_of_code_freeze.txt">announce_end_of_code_freeze.txt</a> to the dev
                     list.</p>
                 </li>
             </ol>