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 07:36:41 UTC
svn commit: r409559 -
/forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Author: crossley
Date: Thu May 25 22:36:41 2006
New Revision: 409559
URL: http://svn.apache.org/viewvc?rev=409559&view=rev
Log:
Tidy up explanation of "Tag".
Other minor text tweaks.
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=409559&r1=409558&r2=409559&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 Thu May 25 22:36:41 2006
@@ -19,14 +19,14 @@
"http://forrest.apache.org/dtd/document-v20.dtd">
<document>
<header>
- <title>How to Release Forrest</title>
+ <title>How to release Forrest</title>
<abstract>This documents the steps that the Release Manager (RM) should follow when doing a Forrest
release.</abstract>
</header>
<body>
<section id="About">
- <title>About this Document</title>
+ <title>About this document</title>
<warning>
This document is still being developed from etc/RELEASE_PROCESS.txt and
some steps will need to be re-arranged.
@@ -44,7 +44,7 @@
</section>
<section id="PrepProject">
- <title>Preparing the Project for the release</title>
+ <title>Preparing the project for the release</title>
<ol>
<li>
<p>The Release Manager (RM) starts the process to finalise the outstanding blocker issues. </p>
@@ -80,7 +80,7 @@
<ol>
<li>
<p>If you have never done a release before or need to refresh your memory, read all about Apache
- Releases in general at <a href="http://www.apache.org/dev/#releases"
+ releases in general at <a href="http://www.apache.org/dev/#releases"
>http://www.apache.org/dev/#releases</a>. Make sure any assistants have read and understood
this as well.</p>
</li>
@@ -130,17 +130,17 @@
</section>
<section id="PrepCodeBase">
- <title>Preparing the Code Base</title>
+ <title>Preparing the code base</title>
<ol>
<li>
- <p>Ensure that there are no copyright issues. The committers and PMC would have been continually
- monitoring this. There are some tools to assist with scanning for issues, e.g. <code>svn:committers/relicense/src/perl/relicense.txt</code> and <a href="svn:committers/tools/"
- >svn:committers/tools/</a>
+ <p>Ensure that there are no license issues. The committers and PMC would have been continually
+ monitoring this. There are some tools to assist with scanning for issues.
+ See <a href="../../roles.html#legal-monitor">further information</a>.
</p>
</li>
<li>
- <p>Ensure that the line-endings and svn:eol-style property are correct for all files. See <a
- href="svn:committers/tools/">svn:committers/tools/</a></p>
+ <p>Ensure that the line-endings and svn:eol-style property are correct for all files.
+ See <a href="../../roles.html#subversion-monitor">further information</a>.</p>
</li>
<li>
<p>Ensure that documentation is ready.</p>
@@ -196,7 +196,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>
@@ -458,7 +458,7 @@
(Remember that you recorded this number earlier.)
</source>
<p> See <a href="http://svn.apache.org/repos/asf/forrest/branches/">http://svn.apache.org/repos/asf/forrest/branches/</a>
- for examples of past branches, e.g. forrest_07_branch.
+ for examples of past branches, e.g. forrest_07_branch
</p>
</li>
</ol>
@@ -503,7 +503,7 @@
</section>
<section id="FinalRel">
- <title>Finalizing the Release</title>
+ <title>Finalizing the release</title>
<p>When a good release candidate has been achieved and affirmed by the vote, we'll finalize the release.</p>
<ol>
@@ -515,16 +515,16 @@
integrate fixes and doc-changes back into trunk. wdyt?</fixme>
</li>
<li>
- <p>If everything looks okay tag SVN by running <code>svn copy -m "Create tag forrest_xy from release
+ <p>Tag SVN by doing <code>'svn copy -m "Create tag forrest_xy from release
branch" \ https://svn.apache.org/repos/asf/forrest/branches/forrest_xy_branch \
- https://svn.apache.org/repos/asf/forrest/tags/forrest_xy</code> from the command line of
- your system, where 'xy' is a compact (without the dots) form of the version number (e.g. 04,
+ https://svn.apache.org/repos/asf/forrest/tags/forrest_xy'</code>
+ where 'xy' is a compact (without the dots) form of the version number (e.g. 04,
041, 05).</p>
+ <p> See <a href="http://svn.apache.org/repos/asf/forrest/tags/">http://svn.apache.org/repos/asf/forrest/tags/</a>
+ for examples of past tags, e.g. forrest_07
+ </p>
<fixme author="fso">If we change procedure to create an rc-branch this will become a merge changes
from trunk then rename rc-branch to final release branch. right?</fixme>
- <p>See <a href="http://svn.apache.org/repos/asf/forrest/tags/"
- >http://svn.apache.org/repos/asf/forrest/tags/</a> for more information.</p>
- <fixme author="fso">What if it doesn't, how do I tell, what do I do?</fixme>
</li>
<li>
<p>Announce the end of the code-freeze by sendung the email-template <a