forrest-site-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r526654 - in /forrest/site/procedures/release: How_to_release.html How_to_release.pdf announce_code_freeze.txt
Date Mon, 09 Apr 2007 05:17:16 GMT
Author: crossley
Date: Sun Apr  8 22:17:15 2007
New Revision: 526654

Automatic publish from forrestbot


Modified: forrest/site/procedures/release/How_to_release.html
--- forrest/site/procedures/release/How_to_release.html (original)
+++ forrest/site/procedures/release/How_to_release.html Sun Apr  8 22:17:15 2007
@@ -806,6 +806,9 @@
+<li>Do any final work, such as license header checks and xml code cleanup.
+                </li>
 <p>Run the following quick tests from the command line of your system to ensure that
all is well:</p>
@@ -927,6 +930,10 @@
 <li>Build the forrestbar and replace site-author/content/xdocs/tools/forrestbar.xpi
+                  Update the etc/RELEASE-NOTES-0.8.txt as described above.
+                </li>
 <li>Commit all of the above changes.</li>
@@ -1029,7 +1036,7 @@
-<a name="N102CF"></a><a name="vote"></a>
+<a name="N102D5"></a><a name="vote"></a>
 <h2 class="underlined_10">Testing the release candidate and voting</h2>
 <div class="section">
 <p>Get Forrest developers to test the actual packges on various platforms.</p>
@@ -1091,7 +1098,7 @@
-<a name="N1030B"></a><a name="FinalRel"></a>
+<a name="N10311"></a><a name="FinalRel"></a>
 <h2 class="underlined_10">Finalizing the release</h2>
 <div class="section">
 <p>When a good release candidate has been achieved and affirmed by the vote, we'll
finalize the release.</p>
@@ -1164,7 +1171,7 @@
-<a name="N10355"></a><a name="UploadAndAnnounce"></a>
+<a name="N1035B"></a><a name="UploadAndAnnounce"></a>
 <h2 class="underlined_10">Upload and announcement</h2>
 <div class="section">
 <p>In this phase we'll upload the new Release, wait for it to be available on most
mirror sites, then
@@ -1325,7 +1332,7 @@
-<a name="N1040B"></a><a name="cleanup"></a>
+<a name="N10411"></a><a name="cleanup"></a>
 <h2 class="underlined_10">Cleanup</h2>
 <div class="section">
@@ -1402,7 +1409,7 @@
-<a name="N10455"></a><a name="conclusion"></a>
+<a name="N1045B"></a><a name="conclusion"></a>
 <h2 class="underlined_10">Conclusion</h2>
 <div class="section">
 <p>All done!</p>

Modified: forrest/site/procedures/release/How_to_release.pdf
Binary files - no diff available.

Modified: forrest/site/procedures/release/announce_code_freeze.txt
--- forrest/site/procedures/release/announce_code_freeze.txt (original)
+++ forrest/site/procedures/release/announce_code_freeze.txt Sun Apr  8 22:17:15 2007
@@ -9,7 +9,7 @@
 Code-freeze means *no* non-essential commits to the trunk
 or to the new release branch. Other branches are free to
+continue. Whiteboard plugins can also continue.
 There should be no code enhancements or new functionality,
 because that could introduce new bugs.
@@ -20,6 +20,9 @@
 Documentation corrections can happen because they will not
 break anything. As long as we do test the documentation
 building just prior to making the final release candidate.
+Although remember that such work should have happened
+prior to the code-freeze. We don't want to build subsequent
+release candidates unless necessary.
 However, if there are important code changes that are
 required you can make a proposal to allow that commit.
@@ -34,7 +37,11 @@
 * Actual release date is [date]
-Now we will go and build the packages which might take
-some time. The next message will tell you where to get
-the release candidate packages and describe how to test.
+Now the Release Manager will do some final changes, such
+as license header checks, xml code cleanup, and changing
+version number information. Then the RM will build the
+packages. These steps may take some time.
+The next message will tell you where to downlaod the
+release candidate packages and describe how to test.

View raw message