Author: buildbot
Date: Fri May 24 09:47:08 2013
New Revision: 862973
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/release-management.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri May 24 09:47:08 2013
@@ -1 +1 @@
-1485858
+1485989
Modified:
websites/staging/sling/trunk/content/documentation/development/release-management.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/release-management.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/release-management.html
Fri May 24 09:47:08 2013
@@ -93,7 +93,11 @@
<div class="toc">
<ul>
<li><a href="#prerequisites">Prerequisites</a></li>
-<li><a href="#staging-the-release-candidates">Staging the Release
Candidates</a></li>
+<li><a href="#staging-the-release-candidates">Staging the Release
Candidates</a><ul>
+<li><a href="#prepare-the-release">Prepare the release</a></li>
+<li><a href="#stage-the-release-for-a-vote">Stage the release for a
vote</a></li>
+</ul>
+</li>
<li><a href="#starting-the-vote">Starting the Vote</a></li>
<li><a href="#wait-for-the-results">Wait for the Results</a></li>
<li><a href="#canceling-the-release">Canceling the Release</a></li>
@@ -157,69 +161,37 @@
</pre></div>
-<ol>
-<li>
-<ul>
-<li>If you experience an error during deployment like a HTTP 401 check your
settings for the required server entries as outlined in the
<em>Prerequisites</em></li>
-</ul>
-</li>
-<li>
-<ul>
-<li>Be sure that the generated artifacts respect the Apache release <a
href="http://www.apache.org/dev/release.html";>rules</a>: NOTICE and LICENSE
files should be present in the META-INF directory within the jar. For -sources
artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3
which is broken. The recommended version at this time is 2.0.4</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>You should verify the deployment under the <a
href="https://repository.apache.org/content/groups/snapshots/org/apache/sling";>snapshot</a>
repository on Apache</li>
-</ul>
-</li>
-<li>
-<p>Prepare the release</p>
-<p>$ mvn release:clean
-$ mvn release:prepare</p>
-</li>
-<li>
-<ul>
-<li>Preparing the release will create the new tag in SVN, automatically
checking in on your behalf</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>If you get a build failure because of an SVN commit problem (namely
<em>The specified baseline is not the latest baseline, so it may not be checked
out.</em>), just repeat the <code>mvn release:prepare</code> command until SVN
is happy. This is based on a known timing issue when using the European SVN
mirror.</li>
-</ul>
-</li>
-<li>
-<p>Stage the release for a vote</p>
-<p>$ mvn release:perform</p>
-</li>
-<li>
-<ul>
-<li>The release will automatically be inserted into a temporary staging
repository for you, see the Nexus <a
href="http://www.sonatype.com/books/nexus-book/reference/staging.html";>staging
documentation</a> for full details</li>
-</ul>
-</li>
-<li>
+<p>If you experience an error during deployment like a HTTP 401 check your
settings for the required server entries as outlined in the
<em>Prerequisites</em></p>
+<p>Make sure the generated artifacts respect the Apache release <a
href="http://www.apache.org/dev/release.html";>rules</a>: NOTICE and LICENSE
files should be present in the META-INF directory within the jar. For -sources
artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3
which is broken. The recommended version at this time is 2.0.4</p>
+<p>You should verify the deployment under the <a
href="https://repository.apache.org/content/groups/snapshots/org/apache/sling";>snapshot</a>
repository on Apache</p>
+<h3 id="prepare-the-release">Prepare the release</h3>
+<div class="codehilite"><pre><span class="nv">$</span> <span
class="nv">mvn</span> <span class="n">release:clean</span>
+<span class="nv">$</span> <span class="nv">mvn</span> <span
class="n">release:prepare</span>
+</pre></div>
+
+
+<p>Preparing the release will create the new tag in SVN, automatically
checking in on your behalf</p>
+<p>If you get a build failure because of an SVN commit problem (namely <em>The
specified baseline is not the latest baseline, so it may not be checked
out.</em>), just repeat the <code>mvn release:prepare</code> command until SVN
is happy. This is based on a known timing issue when using the European SVN
mirror.</p>
+<h3 id="stage-the-release-for-a-vote">Stage the release for a vote</h3>
+<div class="codehilite"><pre><span class="nv">$</span> <span
class="nv">mvn</span> <span class="n">release:perform</span>
+</pre></div>
+
+
+<p>The release will automatically be inserted into a temporary staging
repository for you, see the Nexus <a
href="http://www.sonatype.com/books/nexus-book/reference/staging.html";>staging
documentation</a> for full details</p>
+<p>You can continue to use <code>mvn release:prepare</code> and <code>mvn
release:perform</code> on other sub-projects as necessary on the same machine
and they will be combined in the same staging repository - this is useful when
making a release of multiple Sling modules.</p>
+<p>Then, close the staging repository:</p>
<ul>
-<li>You can continue to use <code>mvn release:prepare</code> and <code>mvn
release:perform</code> on other sub-projects as necessary on the same machine
and they will be combined in the same staging repository - this is useful when
making a release of multiple Sling modules.</li>
-</ul>
-</li>
-<li>Close the staging repository</li>
<li>
-<ul>
-<li>Login to <a
href="https://repository.apache.org";>https://repository.apache.org</a> using
your Apache SVN credentials. Click on <em>Staging</em> on the left. Then click
on <em>org.apache.sling</em> in the list of repositories. In the panel below
you should see an open repository that is linked to your username and IP. Right
click on this repository and select <em>Close</em>. This will close the
repository from future deployments and make it available for others to view. If
you are staging multiple releases together, skip this step until you have
staged everything</li>
-</ul>
+<p>Login to <a
href="https://repository.apache.org";>https://repository.apache.org</a> using
your Apache SVN credentials. Click on <em>Staging</em> on the left. Then click
on <em>org.apache.sling</em> in the list of repositories. In the panel below
you should see an open repository that is linked to your username and IP. Right
click on this repository and select <em>Close</em>. This will close the
repository from future deployments and make it available for others to view. If
you are staging multiple releases together, skip this step until you have
staged everything</p>
</li>
-<li>Verify the staged artifacts</li>
<li>
+<p>Verify the staged artifacts</p>
<ul>
<li>If you click on your repository, a tree view will appear below. You can
then browse the contents to ensure the artifacts are as you expect them. Pay
particular attention to the existence of *.asc (signature) files. If you don't
like the content of the repository, right click your repository and choose
<em>Drop</em>. You can then rollback your release (see <em>Canceling the
Release</em>) and repeat the process</li>
</ul>
</li>
-<li>
-<ul>
-<li>Note the staging repository URL (especially the number at the end of the
URL) you will need this in your vote email</li>
</ul>
-</li>
-</ol>
+<p>Note the staging repository URL (especially the number at the end of the
URL) you will need this in your vote email</p>
<h2 id="starting-the-vote">Starting the Vote</h2>
<p>Propose a vote on the dev list with the closed issues, the issues left, and
the staging repository - for example:</p>
<div class="codehilite"><pre><span class="n">To:</span> <span
class="s">"Sling Developers List"</span> <span
class="sr"><[email protected]></span>
@@ -428,7 +400,7 @@ $ rm the<em>module-version.jar the</em>m
<div class="codehilite"><pre><span class="n">After</span> <span
class="n">updating</span> <span class="n">the</span> <span
class="n">site</span> <span class="n">source</span> <span class="n">it</span>
<span class="n">will</span> <span class="n">generally</span> <span
class="n">take</span> <span class="n">an</span> <span class="n">hour</span>
<span class="ow">or</span> <span class="n">two</span> <span
class="k">until</span> <span class="n">the</span> <span
class="n">changes</span> <span class="n">are</span> <span
class="n">visible</span> <span class="n">on</span> <span class="n">the</span>
<span class="n">web</span><span class="o">.</span>
</pre></div>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
+ Rev. 1485989 by bdelacretaz on Fri, 24 May 2013 09:46:58 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
