You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by bu...@apache.org on 2012/08/22 10:44:29 UTC
svn commit: r829663 - in /websites/staging/ace/trunk/content: ./
dev-doc/release-guide.html
Author: buildbot
Date: Wed Aug 22 08:44:28 2012
New Revision: 829663
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 Wed Aug 22 08:44:28 2012
@@ -1 +1 @@
-1375058
+1375945
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 Wed Aug 22 08:44:28 2012
@@ -186,22 +186,22 @@
</ul>
<h2 id="staging-a-release-candidate">Staging a release candidate</h2>
<p>Staging a release starts by checking out a tagged version of the sources:</p>
-<div class="codehilite"><pre><span class="nv">$ </span>svn co https://svn.apache.org/repos/asf/ace/tags/ace-sources-1.0.0 ace-sources-1.0.0
+<div class="codehilite"><pre><span class="nv">$ </span>svn co https://svn.apache.org/repos/asf/ace/tags/ace-sources-X.Y.Z ace-sources-X.Y.Z
</pre></div>
<p>The next step is to create the source archive:</p>
-<div class="codehilite"><pre><span class="nv">$ </span><span class="nb">cd </span>build
+<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
</pre></div>
-<p>Then you sign the source archive, and create md5 and sha1 signatures for it:</p>
+<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
</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 can be done via "svnpubsub":</p>
+<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
</pre></div>
@@ -211,6 +211,10 @@
<div class="codehilite"><pre>To: <span class="s2">"Apache ACE developers list"</span> <dev@ace.apache.org>
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
+
Please vote to approve this release:
<span class="o">[</span> <span class="o">]</span> +1 Approve the release
<span class="o">[</span> <span class="o">]</span> -1 Veto the release <span class="o">(</span>please motivate<span class="o">)</span>
@@ -237,13 +241,13 @@ 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:</p>
+<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
</pre></div>
-<p>Then update the tag in subversion, for example for the 1.0.0 release like this:</p>
-<div class="codehilite"><pre><span class="nv">$ </span>svn move https://svn.apache.org/repos/asf/ace/tags/ace-sources-1.0.0 https://svn.apache.org/repos/asf/ace/releases/ace-sources-1.0.0 -m <span class="s2">"Apache ACE source release 1.0.0 tagged."</span>
+<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>
</pre></div>