svn commit: r791022 - /websites/staging/rave/trunk/content/rave/release-process.html

[bu...@apache.org]

Author: buildbot
Date: Wed Jun 15 21:55:52 2011
New Revision: 791022

Log:
Staging update by buildbot

Modified:
    websites/staging/rave/trunk/content/rave/release-process.html

Modified: websites/staging/rave/trunk/content/rave/release-process.html
==============================================================================
--- websites/staging/rave/trunk/content/rave/release-process.html (original)
+++ websites/staging/rave/trunk/content/rave/release-process.html Wed Jun 15 21:55:52 2011
@@ -74,18 +74,16 @@
 </pre></div>
 
 
-</li>
-<li>
-<p>Use the latest Sun 1.6.0 JDK</p>
-</li>
+<ol>
+<li>Use the latest Sun 1.6.0 JDK</li>
 <li>Use Maven 3.0.3 or later</li>
-<li>
-<p>Make sure the <a href="release-setup.html">Release Setup</a> steps have been performed.</p>
+<li>Make sure the <a href="release-setup.html">Release Setup</a> steps have been performed.</li>
+</ol>
 </li>
 <li>
-<p>Prepare the source for release:<br />
+<p>Prepare the source for release:   <br />
 </p>
-</li>
+<ol>
 <li>Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly. Also, transition any Resolved issues to the Closed state.</li>
 <li>Update the text files in a working copy of the project root -<ol>
 <li>Update the CHANGELOG based on the Text release reports from JIRA.</li>
@@ -93,49 +91,52 @@
 <li>Commit any changes back to svn </li>
 </ol>
 </li>
-<li>
-<p>Stage any Roadmap or Release landing pages on the site.</p>
+<li>Stage any Roadmap or Release landing pages on the site.</li>
+</ol>
 </li>
 <li>
 <p>Checkout a clean copy of the trunk to release using command line svn. <br />
 </p>
 </li>
 </ol>
-<p><em>Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws off the rat:check processing.</em>
-4. Use <code>mvn verify</code> to verify the source has the required headers before trying to release.
-5. Do a dry run of the release:prepare step.<br />
+<p><em>Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws off the rat:check processing.</em></p>
+<ol>
+<li>
+<p>Use <code>mvn -P pedantic verify</code> to verify the source has the required headers before trying to release.</p>
+</li>
+<li>
+<p>Do a dry run of the release:prepare step:<br />
 </p>
-<p>The dry run will not commit any changes back to SVN and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :
-      * Release version - take the default 
-      * SCM release tag - <em>DO NOT TAKE THE DEFAULT</em>  -: : 0.1-incubating
-      * New development version - take the default 
-      * GPG Passprhase</p>
-<div class="codehilite"><pre>   <span class="nv">$</span> <span class="nv">mvn</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="n">release:prepare</span> <span class="o">-</span><span class="n">DdryRun</span><span class="o">=</span><span class="n">true</span>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">mvn</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="n">release:prepare</span> <span class="o">-</span><span class="n">DdryRun</span><span class="o">=</span><span class="n">true</span>
 </pre></div>
 
 
+</li>
+</ol>
+<p>The dry run will not commit any changes back to SVN and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :
+      * Release version - take the default 
+      * SCM release tag - <em>DO NOT TAKE THE DEFAULT</em>  -: : 0.1-incubating
+      * New development version - take the default
+      * GPG Passprhase<br />
+</p>
 <p><em>If you cancel a release:prepare before it updates the pom.xml versions, then use the release:clean goal to just remove the extra files that were created.</em></p>
 <ol>
-<li>
-<ol>
+<li>Verify that the release process completed as expected<ol>
 <li>The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number.</li>
 <li>
 <p>If other formatting changes have been made you should review the changes and then commit them - <br />
 </p>
 <div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">commit</span> <span class="o">-</span><span class="n">m</span> <span class="s">&quot;fixing formatting for release&quot;</span>
+<span class="mi">3</span><span class="o">.</span> <span class="n">Check</span> <span class="n">release</span><span class="o">.</span><span class="n">properties</span> <span class="ow">and</span> <span class="n">make</span> <span class="n">sure</span> <span class="n">that</span> <span class="n">the</span> <span class="n">scm</span> <span class="n">properties</span> <span class="n">have</span> <span class="n">the</span> <span class="n">right</span> <span class="n">version</span><span class="o">.</span> <span class="n">Sometimes</span> <span class="n">the</span> <span class="n">scm</span> <span class="n">location</span> <span class="n">can</span> <span class="n">be</span> <span class="n">the</span> <span class="n">previous</span> <span class="n">version</span> <span class="ow">not</span> <span class="n">the</span> <span class="k">next</span> <span class="n">version</span><span class="o">.</span>
+<span class="mi">4</span><span class="o">.</span> <span class="n">Verify</span> <span class="n">signatures</span> <span class="p">([</span><span class="n">Verifying</span> <span class="n">release</span> <span class="n">signatures</span><span class="p">](</span><span class="n">http:</span><span class="sr">//i</span><span class="n">ncubator</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/rave/</span><span class="n">release</span><span class="o">-</span><span class="n">process</span><span class="o">.</span><span class="n">html</span><span class="c1">#verify_signatures))</span>
 </pre></div>
 
 
 </li>
 </ol>
-<p>Verify that the release process completed as expected</p>
-<ol>
-<li>Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.</li>
-<li>verify signatures (<a href="http://incubator.apache.org/rave/cwiki/release-process.html#ReleaseProcess-Verifyingreleasesignatures">Verifying release signatures</a>)</li>
-</ol>
 </li>
 <li>
-<p>Once any failures or required updates have been committed to svn, rollback the release prepare files -<br />
+<p>Once any failures or required updates have been committed to svn, rollback the release prepare files:<br />
 </p>
 <div class="codehilite"><pre><span class="nv">$</span> <span class="nv">mvn</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="n">release:rollback</span>
 </pre></div>
@@ -147,8 +148,10 @@
 </li>
 <li>
 <p>Run the "release:prepare" step for real this time. You'll be prompted for the same version information.</p>
-<p><em>Different arguments and steps are required as there are problems with the maven-jar-plugin and maven-release-plugin when using the test-jar goal. See http://jira.codehaus.org/browse/MJAR-68 and http://jira.codehaus.org/browse/MRELEASE-285.</em></p>
-<p>$ mvn release:prepare -Papache-release -DpreparationGoals="clean install cargo:package"</p>
+<div class="codehilite"><pre>  <span class="nv">$</span> <span class="nv">mvn</span> <span class="n">release:prepare</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="o">-</span><span class="n">DpreparationGoals</span><span class="o">=</span><span class="s">&quot;clean install cargo:package&quot;</span>
+</pre></div>
+
+
 </li>
 <li>
 <p>Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.</p>
@@ -187,8 +190,8 @@
 <li>Perform a review of the release and cast your vote. See the following for more details on Apache releases </li>
 </ol>
 <p>Put the release candidate up for a vote</p>
-<p><a href="http://www.apache.org/dev/release.html">http://www.apache.org/dev/release.html</a>
- <a href="http://incubator.apache.org/guides/releasemanagement.html">http://incubator.apache.org/guides/releasemanagement.html</a></p>
+<p><a href="http://www.apache.org/dev/release.html">http://www.apache.org/dev/release.html</a><br />
+<a href="http://incubator.apache.org/guides/releasemanagement.html">http://incubator.apache.org/guides/releasemanagement.html</a></p>
 <ol>
 <li>A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. See - Recovering from a vetoed release</li>
 <li>
@@ -233,8 +236,8 @@
 </ol>
 <p>Promote the staged nexus artifacts -</p>
 <ol>
-<li>Copy the distribution artifacts over to the distribution area</li>
-</ol>
+<li>
+<p>Copy the distribution artifacts over to the distribution area</p>
 <p>$ ssh ${user.name}@people.apache.org<br />
   $ mkdir /www/www.apache.org/dist/incubator/rave/${project.version} <br />
   $ cd /www/www.apache.org/dist/incubator/rave/${project.version} <br />
@@ -243,9 +246,14 @@
   $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.md5 <br />
   $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.sha1  <br />
 </p>
+</li>
+</ol>
 <p><strong>Make sure all the copied files have g+rw set and only o+r set</strong></p>
-<p>$ find . -user ${user.name} -type f | xargs chmod 664
-  $ find . -user ${user.name} -type d | xargs chmod 775</p>
+<div class="codehilite"><pre>  $ find . -user <span class="cp">${</span><span class="n">user</span><span class="o">.</span><span class="n">name</span><span class="cp">}</span> -type f | xargs chmod 664
+  $ find . -user <span class="cp">${</span><span class="n">user</span><span class="o">.</span><span class="n">name</span><span class="cp">}</span> -type d | xargs chmod 775
+</pre></div>
+
+
 <p><em>Note: All of the artifacts are in the maven repos, but we may create an assembly to publish in future releases</em></p>
 <ol>
 <li>Publish the staged website </li>