Author: buildbot
Date: Tue Apr 23 15:27:51 2013
New Revision: 859618
Log:
Staging update by buildbot for ace
Modified:
websites/staging/ace/trunk/content/ (props changed)
websites/staging/ace/trunk/content/dev-doc/release-guide.html
Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 23 15:27:51 2013
@@ -1 +1 @@
-1470938
+1471009
Modified: websites/staging/ace/trunk/content/dev-doc/release-guide.html
==============================================================================
--- websites/staging/ace/trunk/content/dev-doc/release-guide.html (original)
+++ websites/staging/ace/trunk/content/dev-doc/release-guide.html Tue Apr 23
15:27:51 2013
@@ -184,6 +184,7 @@
<p>Before you can start staging a release candidate, you must:</p>
<ul>
<li>Make sure there are no snapshot dependencies anymore.</li>
+<li>Double check that the version you want to create is correctly filled in in
build/build.xml.</li>
<li>Create a tagged version of the sources in preparation of the release
candidate.</li>
</ul>
<h2 id="staging-a-release-candidate">Staging a release candidate</h2>
@@ -192,19 +193,19 @@
</pre></div>
-<p>The next step is to create the source archive:</p>
+<p>The next step is to create the archives:</p>
<div class="codehilite"><pre><span class="nv">$ </span><span class="nb">cd
</span>ace-sources-X.Y.Z/build
-<span class="nv">$ </span>ant -f src-build.xml package-src
+<span class="nv">$ </span>ant package
</pre></div>
-<p>Then you sign the source archive by invoking the following target:</p>
-<div class="codehilite"><pre><span class="nv">$ </span>ant -f src-build.xml
sign-src
+<p>Then you sign archives by invoking the following target:</p>
+<div class="codehilite"><pre><span class="nv">$ </span>ant sign
</pre></div>
-<p>Now you can upload the source archive and the signatures to our development
area, which we use to stage this release candidate. This development area can
be found at https://dist.apache.org/repos/dist/dev/ace and adding files to it
can be done using "svnpubsub" which is taken care of by the following
target:</p>
-<div class="codehilite"><pre><span class="nv">$ </span>ant -f src-build.xml
commit-to-staging
+<p>Now you can upload the archives and the signatures to our development area,
which we use to stage this release candidate. This development area can be
found at https://dist.apache.org/repos/dist/dev/ace and adding files to it can
be done using "svnpubsub" which is taken care of by the following target:</p>
+<div class="codehilite"><pre><span class="nv">$ </span>ant commit-to-staging
</pre></div>
@@ -213,9 +214,11 @@
<div class="codehilite"><pre>To: <span class="s2">"Apache ACE developers
list"</span> <[email protected]>
Subject: <span class="o">[</span>VOTE<span class="o">]</span> Release ACE
version X.Y.Z
-The <span class="nb">source </span>code of Apache ACE version X.Y.Z is
available in our
-staging area here:
-https://dist.apache.org/repos/dist/dev/ace/ace-sources-X.Y.Z
+The <span class="nb">source </span>code of Apache ACE version X.Y.Z is
available,
+along with an archive containing all dependencies and a
+binary release <span class="k">for </span>convenience. They can all be found in
+our staging area here:
+https://dist.apache.org/repos/dist/dev/ace/
Please vote to approve this release:
<span class="o">[</span> <span class="o">]</span> +1 Approve the release
@@ -244,12 +247,12 @@ This vote will be open <span class="k">f
<p>And, depending on the result, continue with either promoting or cancelling
the release below.</p>
<h2 id="promoting-the-release">Promoting the release</h2>
<p>Move the artifacts from the development area to the final release location
at https://dist.apache.org/repos/dist/release/ace by invoking the following
target:</p>
-<div class="codehilite"><pre><span class="nv">$ </span>ant -f src-build.xml
promote-to-release
+<div class="codehilite"><pre><span class="nv">$ </span>ant promote-to-release
</pre></div>
<p>Then update the tag in subversion, for example for the X.Y.Z release like
this:</p>
-<div class="codehilite"><pre><span class="nv">$ </span>svn move
https://svn.apache.org/repos/asf/ace/tags/ace-sources-X.Y.Z
https://svn.apache.org/repos/asf/ace/releases/ace-sources-X.Y.Z -m <span
class="s2">"Apache ACE source release X.Y.Z tagged."</span>
+<div class="codehilite"><pre><span class="nv">$ </span>svn move
https://svn.apache.org/repos/asf/ace/tags/ace-sources-X.Y.Z
https://svn.apache.org/repos/asf/ace/releases/ace-sources-X.Y.Z -m <span
class="s2">"Apache ACE release X.Y.Z tagged."</span>
</pre></div>
@@ -266,7 +269,7 @@ This vote will be open <span class="k">f
<h2 id="cancelling-the-release">Cancelling the release</h2>
<p>Remove the artifacts from the development area:</p>
-<div class="codehilite"><pre><span class="nv">$ </span>ant -f src-build.xml
delete-from-staging
+<div class="codehilite"><pre><span class="nv">$ </span>ant delete-from-staging
</pre></div>
