forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r1042062 - in /forrest/trunk/site-author/content/xdocs/procedures/release: How_to_release.xml propose_release_plan.txt
Date Sat, 04 Dec 2010 00:11:31 GMT
Author: crossley
Date: Sat Dec  4 00:11:31 2010
New Revision: 1042062

URL: http://svn.apache.org/viewvc?rev=1042062&view=rev
Log:
Link to past examples of release plans instead of old template.

Removed:
    forrest/trunk/site-author/content/xdocs/procedures/release/propose_release_plan.txt
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=1042062&r1=1042061&r2=1042062&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 Sat Dec
 4 00:11:31 2010
@@ -298,30 +298,35 @@
       <title>Preparing the Release Plan</title>
       <p>
         Prepare the Release Plan to define the corner stones of the coming
-        release. Deciding the dates and timing that suits everybody will be
-        difficult. However, try to be careful about holiday periods and try to
+        release. Deciding the dates and timing that suits everybody might be
+        difficult. Try to be careful about holiday periods and try to
         find timing that is good to attract the most people to help.
       </p>
-      <ol>
-        <li>Java-Version to test this release</li>
-        <li>Start of code-freeze</li>
-        <li>Start of test-period</li>
-        <li>Vote on release candidate</li>
-        <li>Optional creation of release candidate #2 (when there are bugs)</li>
-        <li>Start of test-period #2</li>
-        <li>Vote on release candidate #2</li>
-        <li>Scheduled release Date</li>
-      </ol>
       <p>
-        Use the email template
-        <a href="propose_release_plan.txt">propose_release_plan.txt</a> to write
-        and propose your plan, then call for a quick vote on the release plan on
-        the dev list.
+        Some items are:
       </p>
+      <ul>
+        <li>Java-Version to test this release</li>
+        <li>The Release Manager</li>
+        <li>Date for end of vote on release plan</li>
+        <li>Date for create release candidate and start of testing period</li>
+        <li>Optional creation of release candidate #2 (when there are bugs)</li>
+        <li>Date for end of vote on the final release candidate</li>
+        <li>Scheduled release date</li>
+      </ul>
       <p>
         Remind people about our <a href="site:guidelines/voting">voting guidelines</a>
and
         <a href="site:guidelines/actions">release actions</a>.
       </p>
+      <p>
+        See past release plans as examples:
+<!--
+        <a href="http://s.apache.org/jI?action=display">0.8</a>
+-->
+        <a href="http://s.apache.org/jI">0.8</a>
+            |
+        <a href="http://s.apache.org/VL5">0.7</a>
+      </p>
       <note>
         There are various reasons for voting on the Release Plan, e.g.
         draws attention to the release process; encourages people to get



Mime
View raw message