forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r782538 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Date Mon, 08 Jun 2009 06:07:19 GMT
Author: crossley
Date: Mon Jun  8 06:07:17 2009
New Revision: 782538

URL: http://svn.apache.org/viewvc?rev=782538&view=rev
Log:
Add note about being brutal with re-scheduling issues.

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=782538&r1=782537&r2=782538&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 Mon Jun
 8 06:07:17 2009
@@ -124,7 +124,9 @@
       </p>
       <p>
         The RM could do the job alone, which enables speedy process. There are
-        not actually many tasks where assistants can help. However it is a good
+        not actually many tasks where assistants can help with the release
+        itself (other than with the pre-release tasks and testing).
+        However it is a good
         idea to have an assistant so as to pass on the knowledge, to help
         document the process, and to perceive potential flaws. More than one
         assistant would probably hinder.
@@ -154,7 +156,11 @@
         job begins after the project is ready to do the release.
       </p>
       <ul>
-        <li>The project updates the Roadmap to schedule the realistic Issues.</li>
+        <li>The project updates the Roadmap to schedule the realistic Issues.
+          Be brutal. If these issues have not been fixed by now, then it is
+          quite okay to re-schedule them to delay until the next development
+          version. See example emails from the lead-up to previous releases.
+        </li>
         <li>The project made good progress towards fixing the Blockers and applying
the outstanding patches.</li>
         <li>The documentation content is ready.</li>
         <li>Plugins have been reviewed and deployed as necessary. Some perhaps need
to



Mime
View raw message