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/23 02:01:25 UTC
svn commit: r408793 -
/forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Author: crossley
Date: Mon May 22 17:01:24 2006
New Revision: 408793
URL: http://svn.apache.org/viewvc?rev=408793&view=rev
Log:
Minor text tidy up in first part of doc.
Better URLs for info about Signing and PGP.
Clarify what to do if project is not ready for release.
Still need to review the main part of the doc (order of
tasks is very important).
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=408793&r1=408792&r2=408793&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 May 22 17:01:24 2006
@@ -37,8 +37,6 @@
<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>
-
- <p>Review the "FIXME" notes below.</p>
</section>
<section id="PrepProject">
@@ -56,24 +54,25 @@
outstanding patches?</p>
</li>
</ul>
- <p>If so send an email to get the project to decide what to do with the remaining issues. Propose to
+ <p>If not, then the project is not yet ready for release. Remember that it
+ is not the RM's job to do this.</p>
+ <p>If so, then send an email to get the project to decide what to do with the remaining issues. Propose to
delay some issues to a future release, encourage people to fix others. See <a
href="http://issues.apache.org/jira/browse/FOR-853">FOR-853</a>. Look at <a
href="http://www.mail-archive.com/dev@forrest.apache.org/msg02310.html">msg02310.html</a>
for an example of such a message.</p>
- <fixme author="fso">What happens if preconditions are not met?</fixme>
</li>
<li>
- <p>Start discussion on Java-Version to use for compiling and testing the realease.</p>
+ <p>Start discussion on Java-Version to use for compiling and testing the release.</p>
</li>
</ol>
</section>
<section id="PrepTeam">
- <title>Peparations for the Release Team</title>
- <p>Getting everybody in your team up to speed with standard procedures and Apache terminology is crucial for
- a successful release.</p>
+ <title>Preparations for the Release Team</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>
<li>
<p>If you have never done a release before or need to refresh your memory, read all about Apache
@@ -84,17 +83,15 @@
<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://wiki.apache.org/incubator/SigningReleases"
- >http://wiki.apache.org/incubator/SigningReleases</a> and <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>
</li>
<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 the file. Instructions on how to
- create pgp-keys for new team members can be found ???</p>
- <fixme author="fso">Add pointer for ???</fixme>
+ 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>
</li>
<li>
<p>Make sure every team member has downloaded and installed the Java-Version to use for compiling
@@ -128,7 +125,7 @@
</note>
</section>
- <section id="PepCodeBase">
+ <section id="PrepCodeBase">
<title>Preparing the Code Base</title>
<ol>
<li>
@@ -155,7 +152,7 @@
</section>
<section id="PrepNewBranch">
- <title>Pepare Release Branch</title>
+ <title>Prepare 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
@@ -184,9 +181,8 @@
<p>Alternative Approach</p>
<ol>
- <li>
- <p>run 'svn status --no-ignore'</p>
- </li>
+ <li> Do 'svn update -r HEAD' to ensure that you are up-to-date. </li>
+ <li> Run 'svn status --no-ignore' </li>
<li>
<p>Delete any extra files you might have added/changed in your local copy. <strong>They must not be
packed with the release.</strong> It must be a pristine copy of the current trunk.</p>
@@ -197,7 +193,7 @@
</section>
<section id="adjustDocs">
- <title>Prepare Docs for next release Cycle</title>
+ <title>Prepare Docs for next release cycle</title>
<fixme author="">I'd suggest the following steps to keep build size small and simplify procedure:</fixme>