forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r526652 - /forrest/trunk/site-author/content/xdocs/procedures/release/announce_code_freeze.txt
Date Mon, 09 Apr 2007 04:57:07 GMT
Author: crossley
Date: Sun Apr  8 21:57:06 2007
New Revision: 526652

URL: http://svn.apache.org/viewvc?view=rev&rev=526652
Log:
Fine-tune the code-freeze text.

Modified:
    forrest/trunk/site-author/content/xdocs/procedures/release/announce_code_freeze.txt

Modified: forrest/trunk/site-author/content/xdocs/procedures/release/announce_code_freeze.txt
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/release/announce_code_freeze.txt?view=diff&rev=526652&r1=526651&r2=526652
==============================================================================
--- forrest/trunk/site-author/content/xdocs/procedures/release/announce_code_freeze.txt (original)
+++ forrest/trunk/site-author/content/xdocs/procedures/release/announce_code_freeze.txt Sun
Apr  8 21:57:06 2007
@@ -5,7 +5,7 @@
 
 Code-freeze means *no* non-essential commits to the trunk
 or to the new release branch. Other branches are free to
-continue.
+continue. Whiteboard plugins can also continue.
 
 There should be no code enhancements or new functionality,
 because that could introduce new bugs.
@@ -16,6 +16,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.
@@ -30,6 +33,10 @@
 * Actual release date is [date]
   [www.timeanddate.com-URL]
 
-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.



Mime
View raw message