Author: buildbot
Date: Wed Apr  4 16:22:57 2012
New Revision: 811510

Log:
Staging update by buildbot for rave

Modified:
    websites/staging/rave/trunk/content/   (props changed)
    websites/staging/rave/trunk/content/release-process.html

Propchange: websites/staging/rave/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Apr  4 16:22:57 2012
@@ -1 +1 @@
-1309478
+1309480

Modified: websites/staging/rave/trunk/content/release-process.html
==============================================================================
--- websites/staging/rave/trunk/content/release-process.html (original)
+++ websites/staging/rave/trunk/content/release-process.html Wed Apr  4 
16:22:57 2012
@@ -95,11 +95,11 @@
 <p>Prepare the source for release:   <br />
 </p>
 <ol>
-<li>Cleanup JIRA so the Fix Version in issues resolved since the last release 
includes this release version correctly. </li>
+<li>Cleanup JIRA so the Fix Version in issues resolved since the last release 
includes this release version correctly.</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>
 <li>Review and update README.txt if needed.</li>
-<li>Commit any changes back to svn </li>
+<li>Commit any changes back to svn</li>
 </ol>
 </li>
 <li>Stage any Roadmap or Release landing pages on the site.</li>
@@ -117,12 +117,11 @@
 <li>
 <p>Do a dry run of the release:prepare step:<br />
 </p>
-<div class="codehilite"><pre><span class="nv">$</span> <span 
class="nv">mvn</span> <span class="o">-</span><span class="n">P</span> <span 
class="n">apache</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">P</span> <span 
class="n">apache</span><span class="o">-</span><span class="n">release</span> 
<span class="n">release:prepare</span> <span class="o">-</span><span 
class="n">DautoVersionSubmodules</span><span class="o">=</span><span 
class="n">true</span> <span class="o">-</span><span 
class="n">DdryRun</span><span class="o">=</span><span class="n">true</span>
 </pre></div>
 
 
-<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 :<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 :</p>
 <ul>
 <li>Release version - take the default </li>
 <li>SCM release tag - <em>DO NOT TAKE THE DEFAULT</em>  - 
${project.version}</li>
@@ -130,8 +129,8 @@
 <li>GPG Passprhase<br />
 </li>
 </ul>
-<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><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>
+<p>The Maven release plugin checks for SNAPSHOT dependencies in pom's. It will 
not complete the prepare goal until all SNAPSHOT dependencies are resolved.</p>
 </li>
 <li>
 <p>Verify that the release process completed as expected</p>
@@ -164,7 +163,7 @@
 <ol>
 <li>
 <p>Run the "release:prepare" step for real this time. You'll be prompted for 
the same version information.</p>
-<p>$ mvn -P apache-release release:prepare</p>
+<p>$ mvn -P apache-release release:prepare -DautoVersionSubmodules=true</p>
 </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>
@@ -180,6 +179,7 @@
 </li>
 <li>
 <p><em>If your local OS userid doesn't match your Apache userid, then you'll 
have to also override the value provided by the OS to Maven for the site-deploy 
step to work. This is known to work for Linux, but not for Mac and unknown for 
Windows.</em></p>
+<p>-Duser.name=[your_apache_uid]</p>
 </li>
 </ul>
 </li>


Reply via email to