Author: buildbot
Date: Mon Jan 4 23:13:22 2016
New Revision: 977063
Log:
Staging update by buildbot for slider
Modified:
websites/staging/slider/trunk/content/ (props changed)
websites/staging/slider/trunk/content/developing/releasing.html
Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan 4 23:13:22 2016
@@ -1 +1 @@
-1722981
+1722982
Modified: websites/staging/slider/trunk/content/developing/releasing.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/releasing.html (original)
+++ websites/staging/slider/trunk/content/developing/releasing.html Mon Jan 4
23:13:22 2016
@@ -336,7 +336,7 @@ anyway.</p>
</pre></div>
-<h3 id="create-the-releaseproperties-file">Create the
<code>../release.properties</code> file<a class="headerlink"
href="#create-the-releaseproperties-file" title="Permanent link">¶</a></h3>
+<h3 id="create-the-releaseproperties-file">Create the release.properties
file<a class="headerlink" href="#create-the-releaseproperties-file"
title="Permanent link">¶</a></h3>
<p>Create a file <code>../release.properties</code> -that is, one directory
above the source tree you are using. This file will be shared
across two cloned copies of the apache git repository.</p>
@@ -353,7 +353,7 @@ Once an RC is voted in, it can be rename
</pre></div>
-<h3 id="make-sure-your-pgp-signature-is-in-slider-distkeys">Make sure your PGP
signature is in <code>slider-dist/KEYS</code><a class="headerlink"
href="#make-sure-your-pgp-signature-is-in-slider-distkeys" title="Permanent
link">¶</a></h3>
+<h3 id="make-sure-your-pgp-signature-is-in-the-distribution-directory">Make
sure your PGP signature is in the distribution directory<a class="headerlink"
href="#make-sure-your-pgp-signature-is-in-the-distribution-directory"
title="Permanent link">¶</a></h3>
<p>Look for your public key in the <code>KEYS</code> file in the
<code>slider-dist</code> directory.
If it is not there, append it it to the file</p>
<h3 id="make-sure-there-are-no-open-staging-repositories">Make sure there are
no open staging repositories<a class="headerlink"
href="#make-sure-there-are-no-open-staging-repositories" title="Permanent
link">¶</a></h3>
@@ -363,7 +363,7 @@ it's not obvious where newly-staged arti
<a
href="https://repository.apache.org/index.html#stagingRepositories";>https://repository.apache.org/index.html#stagingRepositories</a>
and close+drop all staging slider repositories.</p>
<p>Wait until there are none shown in the UI before proceeding.</p>
-<h3 id="configure-the-build-in-releaseproperties">Configure the build in
<code>../release.properties</code><a class="headerlink"
href="#configure-the-build-in-releaseproperties" title="Permanent
link">¶</a></h3>
+<h3 id="configure-the-build-in-releaseproperties">Configure the build in
release.properties<a class="headerlink"
href="#configure-the-build-in-releaseproperties" title="Permanent
link">¶</a></h3>
<p>Create a file <code>../release.properties</code> âthat is, one directory
above the source tree you are using. (That's to keep the source tree
uncontaminated)</p>
<div class="codehilite"><pre><span class="n">slider</span><span
class="p">.</span><span class="n">release</span><span class="p">.</span><span
class="n">branch</span><span class="p">=</span><span
class="n">branches</span><span class="o">/</span><span
class="n">branch</span><span class="o">-</span>0<span class="p">.</span>9
@@ -622,7 +622,7 @@ enough positive votes.</p>
<p>Then follow the instructions on where to email it.</p>
-<h3 id="update-slider-web-site">Update Slider Web site<a class="headerlink"
href="#update-slider-web-site" title="Permanent link">¶</a></h3>
+<h3 id="update-the-slider-web-site">Update the Slider Web Site<a
class="headerlink" href="#update-the-slider-web-site" title="Permanent
link">¶</a></h3>
<p>Update the Slider website as needed. Most of the documents should have been
updated by now to reflect the released version.
<em>The remaining changes should really be modifying the references to the
latest release to the new version.</em></p>
