rave-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r791836 - /websites/staging/rave/trunk/content/rave/release-process.html
Date Wed, 29 Jun 2011 16:17:16 GMT
Author: buildbot
Date: Wed Jun 29 16:17:15 2011
New Revision: 791836

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 29 16:17:15 2011
@@ -68,7 +68,7 @@
     <h3 id="incubator_release_steps_overview">Incubator Release Steps Overview</h3>
 <p>There are two distinct sets of artifacts that are released on independent schedules:
 rave-master &amp; rave-project.  The rave-master is the project metadata (committers,
roles, etc) and only needs to be released when there is a change in the structure of the project
itself (committers, mentors, etc).  The rave-project artifacts are comprised of all rave source
code, binaries and a standalone demo.<br />
 </p>
-<p>The following steps are performed for each of the rave-project and rave-master releases
separately.</p>
+<p>All of the steps below apply to both the master and project releases, unless otherwise
specified.  As an alternative to releasing separately, the projects MAY be released together
as one combined release.  The steps for this can be found below. (<a href="#combined">Combined
Release Steps</a>)</p>
 <h4 id="common_release_steps">Common Release Steps</h4>
 <ol>
 <li>
@@ -183,7 +183,7 @@
 </ul>
 </li>
 <li>
-<p>Verify the release artifacts</p>
+<p>Verify the Nexus release artifacts</p>
 <ol>
 <li>
 <p>Verify the HTML links in site are correct</p>
@@ -208,6 +208,31 @@
 </ol>
 </li>
 <li>
+<p>Build and stage the Demo artifacts (Rave Project releases Only)</p>
+<ol>
+<li>
+<p>Build and sign the standalone demo:<br />
+</p>
+<ul>
+<li>Checkout the tag from SVN </li>
+<li>$ mvn -P dist</li>
+<li>$ gpg -ab ./rave-portal/target/rave-<em>${project.version}</em>-incubating.bin.zip</li>
+<li>$ gpg -ab ./rave-portal/target/rave-<em>${project.version}</em>-incubating.bin.tar.gz</li>
+<li>$ gpg --print-md SHA512 rave-<em>${project.version}</em>-incubating.bin.zip
&gt; rave-<em>${project.version}</em>-incubating.bin.zip.sha</li>
+<li>$ gpg --print-md SHA512 rave-<em>${project.version}</em>-incubating.bin.tar.gz
&gt; rave-<em>${project.version}</em>-incubating.bin.zip.sha</li>
+<li>$ gpg --print-md MD5 rave-<em>${project.version}</em>-incubating.bin.zip
&gt; rave-<em>${project.version}</em>-incubating.bin.zip.md5</li>
+<li>$ gpg --print-md MD5 rave-<em>${project.version}</em>-incubating.bin.tar.gz
&gt; rave-<em>${project.version}</em>-incubating.bin.zip.md5</li>
+</ul>
+</li>
+<li>
+<p>Copy the artifacts to the staging area</p>
+<ul>
+<li>$ scp ./rave-portal/target/rave-<em>${project.version}</em>-incubating.bin.*
${user.name}@people.apache.org:/www/people.apache.org/builds/incubator/rave/${project.version}/</li>
+</ul>
+</li>
+</ol>
+</li>
+<li>
 <p>Put the release candidate up for a vote</p>
 <ol>
 <li>Create a VOTE email thread on rave-dev@ to record votes as replies, like <a
href="release-vote.txt">this</a></li>
@@ -256,20 +281,6 @@
 </ul>
 </li>
 <li>
-<p>Build and sign the standalone demo (for rave-project releases only):<br />
-</p>
-<ul>
-<li>Checkout the tag from SVN </li>
-<li>$ mvn -P dist</li>
-<li>$ gpg -ab ./rave-portal/target/rave-<em>${project.version}</em>-incubating.bin.zip</li>
-<li>$ gpg -ab ./rave-portal/target/rave-<em>${project.version}</em>-incubating.bin.tar.gz</li>
-<li>$ gpg --print-md SHA512 rave-<em>${project.version}</em>-incubating.bin.zip
&gt; rave-<em>${project.version}</em>-incubating.bin.zip.sha</li>
-<li>$ gpg --print-md SHA512 rave-<em>${project.version}</em>-incubating.bin.tar.gz
&gt; rave-<em>${project.version}</em>-incubating.bin.zip.sha</li>
-<li>$ gpg --print-md MD5 rave-<em>${project.version}</em>-incubating.bin.zip
&gt; rave-<em>${project.version}</em>-incubating.bin.zip.md5</li>
-<li>$ gpg --print-md MD5 rave-<em>${project.version}</em>-incubating.bin.tar.gz
&gt; rave-<em>${project.version}</em>-incubating.bin.zip.md5</li>
-</ul>
-</li>
-<li>
 <p>Copy the distribution artifacts over to the distribution area (for rave-project
only)<br />
 </p>
 <ul>
@@ -286,15 +297,13 @@
 </li>
 <li>$ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-parent-${project.version}-source-release.zip.sha1
 <br />
 </li>
+<li>$ cp -rfv /www/people.apache.org/builds/incubator/rave/${project.version}/* ./</li>
+<li>$ rm -rfv /www/people.apache.org/builds/incubator/rave/${project.version}</li>
 <li>
 <p>Make sure all the copied files have g+rw set and only o+r set</p>
 <p>$ find . -user ${user.name} -type f | xargs chmod 664<br />
    $ find . -user ${user.name} -type d | xargs chmod 775</p>
 </li>
-<li>
-<p>$ exit</p>
-</li>
-<li>$ scp ./rave-portal/target/rave-<em>${project.version}</em>-incubating.bin.*
${user.name}@people.apache.org:/www/www.apache.org/dist/incubator/rave/${project.version}/</li>
 </ul>
 </li>
 <li>
@@ -318,22 +327,18 @@
 <p>[CANCELED]</p>
 </li>
 <li>
-<p>Rollback the version upgrades in trunk by either -</p>
-<ol>
-<li>
-<p>Restore the 0.1-rc1.tar.gz and run</p>
-<p>$ mvn -Papache-release release:rollback</p>
-</li>
-<li>
-<p>Manually revert the versions in trunk to the prior version and commit</p>
-</li>
-</ol>
-</li>
-<li>
 <p>Delete the svn tag created by the release:perform step -</p>
 <p>$ svn del https://svn.apache.org/repos/asf/incubator/rave/tags/0.1-incubating -m
"deleting tag from rolled back release"</p>
 </li>
 <li>
+<p>Delete the build artifacts on people &amp; www         <br />
+</p>
+<ul>
+<li>$ rm -rfv /www/people.apache.org/builds/incubator/rave/${project.version}</li>
+<li>$ rm -rfv /www/www.apache.org/dist/incubator/rave/${project.version}</li>
+</ul>
+</li>
+<li>
 <p>Drop the nexus staging repo</p>
 <ol>
 <li>https://repository.apache.org/index.html</li>
@@ -343,12 +348,11 @@
 </ol>
 </li>
 <li>
-<p>Remote the staged site</p>
+<p>Remove the staged site</p>
 </li>
 <li>
-<p>Make the required updates that caused the vote to be canceled</p>
+<p>Make the required updates that caused the vote to be canceled during the next release
cycle</p>
 </li>
-<li>Spin another release candidate!</li>
 </ol>
 <a name="verify_signatures" />
 
@@ -364,6 +368,25 @@
 <p>You'll need to look at the output to ensure it contains only good signatures -</p>
 <p>gpg: Good signature from ...
 gpg: Signature made ...</p>
+<a name="combined" />
+
+<h4 id="combined_release">Combined Release</h4>
+<p>In order to perform a combined release of the rave-master and rave-project trunks,
do the following:<br />
+</p>
+<ul>
+<li>Perform Steps 1-9 of the <a href="#release-steps">release</a> for Rave
Master &amp; Rave Project<br />
+<ul>
+<li>Do NOT perform step 10 until steps 1-9 have been completed for BOTH projects<br
/>
+</li>
+</ul>
+</li>
+<li>Execute the remaining steps using the following e-mail templates<br />
+<ul>
+<li><a href="PPMC_Combined.txt">PPMC Release Vote</a><br />
+</li>
+</ul>
+</li>
+</ul>
   </div>
 
   <div id="footer">



Mime
View raw message