You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rave.apache.org by bu...@apache.org on 2012/06/30 01:31:40 UTC

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

Author: buildbot
Date: Fri Jun 29 23:31:39 2012
New Revision: 823788

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 Fri Jun 29 23:31:39 2012
@@ -1 +1 @@
-1355152
+1355602

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 Fri Jun 29 23:31:39 2012
@@ -138,24 +138,14 @@
 <p>Verify that the release process completed as expected</p>
 <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>
-</pre></div>
-
-
-</li>
-<li>
-<p>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.</p>
-</li>
+<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="#verify_signatures">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>Cleanup the release prepare files again:<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:rollback</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:clean</span>
 </pre></div>
 
 
@@ -189,9 +179,6 @@
 <p>Verify the Nexus release artifacts</p>
 <ol>
 <li>
-<p>Verify the HTML links in site are correct</p>
-</li>
-<li>
 <p>Verify the staged artifacts in the nexus repo   <br />
 </p>
 <ul>
@@ -219,19 +206,19 @@
 <ul>
 <li>Checkout the tag from SVN </li>
 <li>$ mvn -P dist</li>
-<li>$ gpg -ab ./rave-portal/target/rave-<em>${project.version}</em>.bin.zip</li>
-<li>$ gpg -ab ./rave-portal/target/rave-<em>${project.version}</em>.bin.tar.gz</li>
-<li>$ gpg --print-md SHA512 rave-<em>${project.version}</em>.bin.zip &gt; rave-<em>${project.version}</em>.bin.zip.sha</li>
-<li>$ gpg --print-md SHA512 rave-<em>${project.version}</em>.bin.tar.gz &gt; rave-<em>${project.version}</em>.bin.zip.sha</li>
-<li>$ gpg --print-md MD5 rave-<em>${project.version}</em>.bin.zip &gt; rave-<em>${project.version}</em>.bin.zip.md5</li>
-<li>$ gpg --print-md MD5 rave-<em>${project.version}</em>.bin.tar.gz &gt; rave-<em>${project.version}</em>.bin.zip.md5</li>
+<li>$ gpg -ab ./rave-portal/target/apache-rave-<em>${project.version}</em>.bin.zip</li>
+<li>$ gpg -ab ./rave-portal/target/apache-rave-<em>${project.version}</em>.bin.tar.gz</li>
+<li>$ gpg --print-md SHA512 apache-rave-<em>${project.version}</em>.bin.zip &gt; apache-rave-<em>${project.version}</em>.bin.zip.sha</li>
+<li>$ gpg --print-md SHA512 apache-rave-<em>${project.version}</em>.bin.tar.gz &gt; apache-rave-<em>${project.version}</em>.bin.tar.gz.sha</li>
+<li>$ gpg --print-md MD5 apache-rave-<em>${project.version}</em>.bin.zip &gt; apache-rave-<em>${project.version}</em>.bin.zip.md5</li>
+<li>$ gpg --print-md MD5 apache-rave-<em>${project.version}</em>.bin.tar.gz &gt; apache-rave-<em>${project.version}</em>.bin.tar.gz.md5</li>
 </ul>
 </li>
 <li>
 <p>Copy the artifacts to the staging area</p>
 <ul>
 <li>$ ssh people.apache.org mkdir /www/people.apache.org/builds/rave/${project.version}</li>
-<li>$ scp ./rave-portal/target/rave-<em>${project.version}</em>.bin.* ${user.name}@people.apache.org:/www/people.apache.org/builds/rave/${project.version}/</li>
+<li>$ scp ./rave-portal/target/apache-rave-<em>${project.version}</em>.bin.* ${user.name}@people.apache.org:/www/people.apache.org/builds/rave/${project.version}/</li>
 <li>Verify they are downloadable from http://people.apache.org/builds/rave/${project.version}/</li>
 </ul>
 </li>