You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2006/05/26 09:20:55 UTC
svn commit: r409576 -
/forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Author: crossley
Date: Fri May 26 00:20:55 2006
New Revision: 409576
URL: http://svn.apache.org/viewvc?rev=409576&view=rev
Log:
Add section "Who is the Release Manager" to explain the person, the role, and
the decision making. It is a one-person role, but assistance is good.
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=409576&r1=409575&r2=409576&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 Fri May 26 00:20:55 2006
@@ -42,7 +42,26 @@
<p>It is not the Release Manager's job to fix bugs nor address blocker issues. The RM job begins when the
project is ready to do the release.</p>
</section>
-
+ <section id="rm">
+ <title>Who is the Release Manager</title>
+ <p>The Release Manager is a single person who makes all the decisions regarding the
+ actual preparations and the doing of the release.
+ Many projects have the same release manager for years.
+ The project developers have the role of testing, fixing issues,
+ and voting for the release candidate.
+ The votes of the PMC will decide whether the product is fit for release.
+ </p>
+ <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.
+ More than one assistant would probably hinder.
+ </p>
+ <p>The RM should be comfortable with using SVN and be familiar with
+ the ASF hardware, with the distribution mirror system, and with ASF release procedures.
+ The following notes are terse. If you don't understand, then probably not ready to be RM.
+ </p>
+ </section>
<section id="PrepProject">
<title>Preparing the project for the release</title>
<ol>
@@ -73,8 +92,8 @@
</ol>
</section>
- <section id="PrepTeam">
- <title>Preparations for the Release Team</title>
+ <section id="PrepRM">
+ <title>Preparations for the Release Manager</title>
<p>Particularly the Release Manager, but also anyone assisting, needs to be familiar
with standard procedures and Apache terminology. This is crucial for a successful release.</p>
<ol>
@@ -85,9 +104,9 @@
this as well.</p>
</li>
<li>
- <p>Make sure every team member is familiar with the process of signing releases and generating MD5
- and PGP. You'll find some more info at <a
- href="http://www.apache.org/dev/release-signing.html">Signing Releases></a> and <a
+ <p>Be familiar with the process of signing releases and generating MD5
+ and PGP. Some more info is at <a
+ href="http://www.apache.org/dev/release-signing.html">Signing Releases</a> and <a
href="http://forrest.apache.org/mirrors.cgi#verify"
>http://forrest.apache.org/mirrors.cgi#verify</a>
</p>
@@ -95,19 +114,22 @@
<li>
<p>Ensure that as many PMC members as possible have their PGP keys in the KEYS file in Forrest's
root directory. Instructions on how to add keys are included in that file. Instructions on how to
- create and manage pgp-keys can be found at the abovementioned references.</p>
+ create and manage PGP keys can be found at the abovementioned references.</p>
</li>
<li>
- <p>Make sure every team member has downloaded and installed the Java-Version to use for compiling
- the release. Downloading and installing that version should be done well ahead of time to avoid
- delays.</p>
+ Make sure that the network connection is reliable and efficient.
+ </li>
+ <li>
+ <p>Install the Java-Version that has been agreed for compiling the release.
+ Do this well ahead of time to avoid delays, and ensure that Forrest works for you.
+ </p>
</li>
</ol>
</section>
<section id="PrepRelPlan">
- <title>Prepare the Release Plan</title>
+ <title>Preparing the Release Plan</title>
<p>Prepare the Release Plan to define the corner stones of the coming release</p>
<ol>
<li>Java-Version to test this release</li>
@@ -154,7 +176,7 @@
</section>
<section id="PrepNewBranch">
- <title>Prepare Release Branch</title>
+ <title>Preparing Release Branch</title>
<fixme author="fso">We need to discuss order from here on. My idea is to adjust docs before we enter code
freeze to save time later. But if the rc fails and release is postponed might need to roll back changes
@@ -196,7 +218,7 @@
</section>
<section id="adjustDocs">
- <title>Prepare docs for next release cycle</title>
+ <title>Preparing docs for next release cycle</title>
<fixme author="">I'd suggest the following steps to keep build size small and simplify procedure:</fixme>