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 2011/06/20 19:01:09 UTC
svn commit: r791286 - in /websites/staging/rave/trunk/content/rave:
release-process.html release-setup.html
Author: buildbot
Date: Mon Jun 20 17:01:09 2011
New Revision: 791286
Log:
Staging update by buildbot
Modified:
websites/staging/rave/trunk/content/rave/release-process.html
websites/staging/rave/trunk/content/rave/release-setup.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 Mon Jun 20 17:01:09 2011
@@ -64,20 +64,30 @@
<div id="content">
<h1 class="title">Release Process</h1>
- <h3 id="incubator_release_steps">Incubator Release Steps</h3>
+ <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 & 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>
+<h4 id="common_release_steps">Common Release Steps</h4>
<ol>
-<li>Environment setup for releasing artifacts (same for SNAPSHOTs and releases) -</li>
<li>
-<p>Increase the default Java heap available to Maven (required for Java SE 6)<br />
+<p>Environment setup for releasing artifacts (same for SNAPSHOTs and releases) <br />
</p>
-<div class="codehilite"><pre><span class="n">export</span> <span class="n">MAVEN_OPTS</span><span class="o">=</span><span class="s">"-Xmx1024m -XX:MaxPermSize=256m"</span>
-</pre></div>
-
-
<ol>
-<li>Use the latest Sun 1.6.0 JDK</li>
-<li>Use Maven 3.0.3 or later</li>
-<li>Make sure the <a href="release-setup.html">Release Setup</a> steps have been performed.</li>
+<li>
+<p>Increase the default Java heap available to Maven (required for Java SE 6) <br />
+</p>
+<p>export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m" </p>
+</li>
+<li>
+<p>Use the latest Sun 1.6.0 JDK</p>
+</li>
+<li>
+<p>Use Maven 3.0.3 or later</p>
+</li>
+<li>
+<p>Make sure the <a href="release-setup.html">Release Setup</a> steps have been performed.</p>
+</li>
</ol>
</li>
<li>
@@ -97,48 +107,52 @@
<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></p>
-<ol>
+</li>
<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>
-<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">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>
</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>
+<ul>
+<li>Release version - take the default </li>
+<li>SCM release tag - <em>DO NOT TAKE THE DEFAULT</em> -: : 0.1-incubating</li>
+<li>New development version - take the default</li>
+<li>GPG Passprhase<br />
</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 />
+</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>
+</li>
+<li>
+<p>Verify that the release process completed as expected</p>
<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">"fixing formatting for release"</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>
+<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>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>
-<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>
+<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>
</pre></div>
@@ -148,7 +162,7 @@
</li>
<li>
<p>Run the "release:prepare" step for real this time. You'll be prompted for the same version information.</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">"clean install cargo:package"</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">dist</span> <span class="n">release:prepare</span>
</pre></div>
@@ -237,7 +251,7 @@
<p>Promote the staged nexus artifacts -</p>
<ol>
<li>
-<p>Copy the distribution artifacts over to the distribution area</p>
+<p>Copy the distribution artifacts over to the distribution area (for rave-project only)</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 />
@@ -306,6 +320,8 @@
</li>
<li>Spin another release candidate!</li>
</ol>
+<a name="verify_signatures" />
+
<h4 id="verifying_release_signatures">Verifying release signatures</h4>
<p>On unix platforms the following command can be executed -</p>
<div class="codehilite"><pre> for file in `find . -type f -iname '*.asc'`
Modified: websites/staging/rave/trunk/content/rave/release-setup.html
==============================================================================
--- websites/staging/rave/trunk/content/rave/release-setup.html (original)
+++ websites/staging/rave/trunk/content/rave/release-setup.html Mon Jun 20 17:01:09 2011
@@ -149,6 +149,10 @@
<p>Following the instructions in http://people.apache.org/~henkp/trust/ and ask multiple (at least 3) current Apache committers to sign your public key.</p>
</li>
</ol>
+<h4 id="configure_maven">Configure Maven</h4>
+<ol>
+<li>Update your ~/.m2/settings.xml with the properties from <a href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env">Publishing Maven Artifacts</a></li>
+</ol>
</div>
<div id="footer">