svn commit: r396364 - /forrest/trunk/etc/RELEASE_PROCESS.txt

[cr...@apache.org]

Author: crossley
Date: Sun Apr 23 18:13:26 2006
New Revision: 396364

URL: http://svn.apache.org/viewcvs?rev=396364&view=rev
Log:
Expand the info about Release Plan, and make sure that we vote on it this time.

Modified:
    forrest/trunk/etc/RELEASE_PROCESS.txt

Modified: forrest/trunk/etc/RELEASE_PROCESS.txt
URL: http://svn.apache.org/viewcvs/forrest/trunk/etc/RELEASE_PROCESS.txt?rev=396364&r1=396363&r2=396364&view=diff
==============================================================================
--- forrest/trunk/etc/RELEASE_PROCESS.txt (original)
+++ forrest/trunk/etc/RELEASE_PROCESS.txt Sun Apr 23 18:13:26 2006
@@ -29,8 +29,14 @@
 - Ensure that all relevant plugins have been deployed to plugins/0.8-dev/
   See other notes at plugins/RELEASE_PROCESS.txt
 
-- Announce the release plan to the dev list. Define when the code freeze
-  commences, when the vote ends etc. See email templates at end of this file.
+- Prepare the Release Plan and call for a quick vote on the dev list.
+  There are various reasons for voting on the Release Plan, e.g. makes people
+  aware that a code-freeze is about to happen; encourage them to get involved
+  with the release; ensure that the date is suitable and people will be around
+  to test and then vote on the actual release. See a good discussion
+  at http://marc.theaimsgroup.com/?t=114296877800003
+  Define when the code freeze commences, when the vote ends etc.
+  See email templates at end of this file.
   Send a reminder when the code-freeze commences.
   
   - Check out a fresh copy from SVN to make sure you have no local