Author: crossley Date: Wed Nov 30 07:45:57 2011 New Revision: 1208312 URL: http://svn.apache.org/viewvc?rev=1208312&view=rev Log: Publish from forrestbot
Modified: forrest/site/guidelines.html forrest/site/procedures/release/How_to_release.html Modified: forrest/site/guidelines.html URL: http://svn.apache.org/viewvc/forrest/site/guidelines.html?rev=1208312&r1=1208311&r2=1208312&view=diff ============================================================================== --- forrest/site/guidelines.html (original) +++ forrest/site/guidelines.html Wed Nov 30 07:45:57 2011 @@ -749,7 +749,8 @@ document.write("Last Published: " + docu <h3 class="underlined_5">Actions</h3> <p> This section describes the various actions which are undertaken within - the project, the corresponding approval required for that action, and + the project, the corresponding + <a href="#approvals">approval</a> required for that action, and those who have binding votes over the action. </p> <table class="ForrestTable" cellspacing="1" cellpadding="4"> @@ -806,7 +807,7 @@ document.write("Last Published: " + docu required to accept the release as an official release of the project. A release cannot be vetoed (hence lazy majority). - The <a href="procedures/release/How_to_release.html#rm">Release Manager</a> + A <a href="procedures/release/How_to_release.html#rm">Release Manager</a> might choose to get an issue resolved or re-schedule, but that is their <a href="procedures/release/How_to_release.html#decisionRM">decision</a>. </td> Modified: forrest/site/procedures/release/How_to_release.html URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/How_to_release.html?rev=1208312&r1=1208311&r2=1208312&view=diff ============================================================================== --- forrest/site/procedures/release/How_to_release.html (original) +++ forrest/site/procedures/release/How_to_release.html Wed Nov 30 07:45:57 2011 @@ -235,7 +235,7 @@ document.write("Last Published: " + docu <h1>How to release Forrest</h1> <div id="front-matter"> <div class="abstract"> - This documents the steps that the Release Manager (RM) should follow when + This document provides guidelines for the steps that a Release Manager (RM) should follow when doing a Forrest release. </div> <div id="minitoc-area"> @@ -244,7 +244,7 @@ document.write("Last Published: " + docu <a href="#About">About this document</a> </li> <li> -<a href="#rm">Who is the Release Manager</a> +<a href="#rm">Who is a Release Manager</a> </li> <li> <a href="#prep">Tasks to be done by the project before the release can start</a> @@ -308,7 +308,7 @@ document.write("Last Published: " + docu </div> </div> <p> - This documents the steps that the Release Manager (RM) should follow + This document provides guidelines for the steps that a Release Manager (RM) should follow when doing a Forrest release. Note that it might have mistakes - we seem to discover something new each time and some steps might need to happen in a different order. Fine tune these notes for next time. Do some @@ -342,13 +342,15 @@ document.write("Last Published: " + docu </div> <a name="rm"></a> -<h2 class="underlined_10">Who is the Release Manager</h2> +<h2 class="underlined_10">Who is a Release Manager</h2> <div class="section"> <p> - The Release Manager is a single person who does the final work of the - release process to prepare and sign release packages, co-ordinate + A Release Manager is a Forrest committer who does the work of the + release process to prepare a release candidate and sign release packages, co-ordinate testing and voting, uploading to the dist area and ensuring mirrors, and sending the announcement. + See the <a href="http://httpd.apache.org/dev/release.html">release guidelines</a> + of the HTTP Server project, which has useful notes about the RM role. </p> <p> The project developers have the role of preparing the product to release @@ -357,8 +359,7 @@ document.write("Last Published: " + docu </p> <p> The RM makes all the <a href="#decisionRM">calls</a> regarding the actual preparations and the - doing of the release. Many projects have the same release manager for - years. + doing of the release. </p> <p> The RM could do the job alone, which enables speedy process. There are @@ -382,7 +383,7 @@ document.write("Last Published: " + docu </p> <p> The following notes are terse. If you don't understand, then - probably not ready to be RM. + probably not ready to be an RM. </p> </div>