forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r1065493 - /forrest/trunk/site-author/content/xdocs/procedures/release/announce_code_freeze.txt
Date Mon, 31 Jan 2011 06:56:32 GMT
Author: crossley
Date: Mon Jan 31 06:56:31 2011
New Revision: 1065493

URL: http://svn.apache.org/viewvc?rev=1065493&view=rev
Log:
Only essential changes.

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?rev=1065493&r1=1065492&r2=1065493&view=diff
==============================================================================
--- 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 Mon
Jan 31 06:56:31 2011
@@ -13,9 +13,9 @@ because that could introduce new bugs.
 The main aim is to find and fix important bugs. Any minor
 issues are delayed until after release (add to Jira).
 
-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.
+Essential documentation corrections can happen because they
+will not break anything. As long as we do test the documentation
+building just prior to making any 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.



Mime
View raw message