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

[cr...@apache.org]

Author: crossley
Date: Wed Dec  1 05:38:19 2010
New Revision: 1040875

URL: http://svn.apache.org/viewvc?rev=1040875&view=rev
Log:
Re-word some notes about the release plan.

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?rev=1040875&r1=1040874&r2=1040875&view=diff
==============================================================================
--- 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 Dec  1 05:38:19 2010
@@ -322,9 +322,9 @@
         <a href="site:guidelines/actions">release actions</a>.
       </p>
       <note>
-        There are various reasons for voting on the Release Plan, e.g. makes
-        people aware that a code-freeze is about to happen; draws attention to
-        the release process; encourages people to get involved; ensures that the
+        There are various reasons for voting on the Release Plan, e.g.
+        draws attention to the release process; encourages people to get
+        involved; prompts people get their changes committed; ensures that the
         date is suitable and
         people will be around to test and then vote on the actual release. This
         ensures that it is the PMC as a whole that prepares and issues the