forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r522740 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Date Tue, 27 Mar 2007 04:19:41 GMT
Author: crossley
Date: Mon Mar 26 21:19:40 2007
New Revision: 522740

URL: http://svn.apache.org/viewvc?view=rev&rev=522740
Log:
Ensure that people realise why we vote. Ensure that we vote on final actual relase packages.

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?view=diff&rev=522740&r1=522739&r2=522740
==============================================================================
--- 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 Mar
26 21:19:40 2007
@@ -51,7 +51,7 @@
             <p>The RM could do the whole job alone, which enables speedy process.
               There are not actually many tasks where assistants can help.
               However it is a good idea to have an assistant so as to pass
-              on the knowledge, to help document it, and to perceive potential flaws.
+              on the knowledge, to help document the process, and to perceive potential flaws.
               More than one assistant would probably hinder.
             </p>
             <p>The RM should be comfortable with using SVN and be familiar with
@@ -165,8 +165,12 @@
                 propose your plan, then call for a quick vote on the release plan on the
dev list.</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; 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 <a
-                    href="http://marc.theaimsgroup.com/?t=114296877800003">in the archives</a>
+                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 release,
+                rather than an individual. Such procedures give us the protection
+                accorded by the ASF being a corporation.
+                See a good discussion
+                <a href="http://marc.theaimsgroup.com/?t=114296877800003">in the archives</a>.
             </note>
         </section>
 
@@ -530,6 +534,10 @@
                     release candidate.</li>
                 <li>Tally the votes and report the result to the dev list.</li>
             </ol>
+            <note>
+              It is vitally important that people review and vote against the actual final
release packages
+              (and not just against their SVN working copy).
+            </note>
         </section>
 
         <section id="FinalRel">



Mime
View raw message