Author: buildbot
Date: Wed Feb 25 04:22:59 2015
New Revision: 941420
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 Wed Feb 25 04:22:59 2015
@@ -1 +1 @@
-1660959
+1662166
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 Wed Feb 25
04:22:59 2015
@@ -216,19 +216,24 @@ starting to make a release</em></p>
Slider release.</p>
<p><em>5.</em> Check ASF headers dependencies</p>
<p>Ensure the rat check is clean. This rejects files which lack ASF headers</p>
-<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">clean</span> <span class="n">apache</span><span
class="o">-</span><span class="nb">rat</span><span class="p">:</span><span
class="n">check</span> <span class="o">-</span><span class="n">Prat</span>
+<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">clean</span>
+<span class="n">mvn</span> <span class="n">apache</span><span
class="o">-</span><span class="nb">rat</span><span class="p">:</span><span
class="n">check</span> <span class="o">-</span><span class="n">Prat</span>
</pre></div>
<h3 id="checking-licenses">Checking licenses</h3>
<p>Maven can check that all dependent artifacts have valid licenses</p>
-<p>For pom-only projects (including the root slider project)</p>
-<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">license</span><span class="p">:</span><span
class="n">aggregate</span><span class="o">-</span><span
class="n">add</span><span class="o">-</span><span class="n">third</span><span
class="o">-</span><span class="n">party</span> <span class="o">-</span><span
class="n">Dlicense</span><span class="p">.</span><span
class="n">useMissingFile</span>
+<p>For modules which publish JARs (<code>slider-core</code> and
<code>slider-funtest</code>),
+run the third party check for JARs. If you run this at the top level project
+it will do it for the relevant sub projects.</p>
+<div class="codehilite"><pre> <span class="c"># in slider toplevel dir</span>
+ <span class="n">mvn</span> <span class="nb">license</span><span
class="p">:</span><span class="n">add</span><span class="o">-</span><span
class="n">third</span><span class="o">-</span><span class="n">party</span>
<span class="o">-</span><span class="n">Dlicense</span><span
class="p">.</span><span class="n">useMissingFile</span>
</pre></div>
-<p>for projects which publish JARs</p>
-<div class="codehilite"><pre> <span class="n">mvn</span> <span
class="n">license</span><span class="p">:</span><span class="n">add</span><span
class="o">-</span><span class="n">third</span><span class="o">-</span><span
class="n">party</span> <span class="o">-</span><span
class="n">Dlicense</span><span class="p">.</span><span
class="n">useMissingFile</span>
+<p>You also need to verify that the slider-assembly module is compliant</p>
+<div class="codehilite"><pre><span class="c"># in slider-assembly</span>
+<span class="n">mvn</span> <span class="nb">license</span><span
class="p">:</span><span class="n">aggregate</span><span class="o">-</span><span
class="n">add</span><span class="o">-</span><span class="n">third</span><span
class="o">-</span><span class="n">party</span> <span class="o">-</span><span
class="n">Dlicense</span><span class="p">.</span><span
class="n">useMissingFile</span>
</pre></div>
@@ -236,15 +241,18 @@ Slider release.</p>
To fix this, make sure that the (generated or updated) file
<code>src/license/THIRD-PARTY.properties</code>
has an entry for every dependency without a license, declaring what their
license is.</p>
<h3 id="signing-keys">Signing keys</h3>
-<p>Verify your PGP key is provided to Apache. </p>
+<p>Verify your GPG key is provided to Apache. </p>
<p>Apache verifies that distributions are correctly signed.
Login to <a href="https://id.apache.org";>https://id.apache.org</a> and verify
the
-fingerprint of PGP key used to sign above is provided. (<code>gpg
--fingerprint</code>)
-Upload your PGP public key only to <code>/home/$ASF_USER/.pgpkey</code></p>
+fingerprint of GPG key used to sign above is provided. (<code>gpg
--fingerprint</code>)
+Upload your GPG public key only to <code>/home/$ASF_USER/.pgpkey</code></p>
<div class="codehilite"><pre><span class="n">scp</span> <span
class="n">public</span><span class="o">-</span><span class="n">key</span><span
class="p">.</span><span class="n">asc</span> <span class="n">people</span><span
class="p">.</span><span class="n">apache</span><span class="p">.</span><span
class="n">org</span><span class="p">:.</span><span class="n">pgpkey</span>
</pre></div>
+<p><em>Tip</em>: if you are creating a new key, remember what
password/passphrase you have
+given it. Then generate a revocation certificate and store it somewhere, so
+that you can revoke the published key.</p>
<h5 id="note-profiles">Note: Profiles</h5>
<p>The slider POMs offer different profiles of Hadoop versions to build
against. The instructions
below do not choose one. If a profile is needed, append it to all the maven
commands.</p>
@@ -394,8 +402,15 @@ anyway.</p>
</pre></div>
+<p>The profile <code>apache-release</code> is used to select a subset of the
app packages,
+because the default builds of these weren't usable and had odd version numbers
+too.</p>
<h2 id="git-preparation">Git preparation</h2>
-<p>The maven automated release adds its own git tags and pushes things up to a
branch. All work must be done on a branch created for the release process, so
as to not interfere with the rest of the development. You are likely to end up
rolling back the branch, force-pushing changes &c, so cannot actively share
the branch with anyone.</p>
+<p>The maven automated release adds its own git tags and pushes things up to a
branch.
+All work must be done on a branch created for the release process, so as to
+not interfere with the rest of the development.
+You are likely to end up rolling back the branch, force-pushing changes etc.,
+so cannot actively share the branch with anyone.</p>
<h3 id="clone-the-repo">Clone the repo.</h3>
<p>Don't release from your development dir; do it somewhere clean. Why so?
Easier to clean up and guaranteed isolation.</p>
<p>In a directory of your choice</p>
@@ -417,15 +432,19 @@ anyway.</p>
<h2 id="test-deploy-a-snapshot">Test Deploy a snapshot</h2>
-<p>This pushes up a <code>-SNAPSHOT</code> version to the ASF snapshot repo.
It doesn't change the POMs; it does verify that you have the basic upload
settings, signing keys etc.</p>
+<p>This pushes up a <code>-SNAPSHOT</code> version to the ASF snapshot repo.
+It doesn't change the POMs; it does verify that you have the basic upload
settings, signing keys etc.</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">clean</span> <span class="n">deploy</span> $<span
class="n">RELARGS</span> <span class="o">-</span><span
class="n">Darguments</span><span class="p">=</span>"$<span
class="n">RELARGS</span>"
</pre></div>
<p>Assuming that all the test and integration tests have already been
successful on normal workspace, you can skip the tests</p>
<p>After the upload has completed, the complete archives will be in the
version-specific subdirectory of</p>
-<p>https://repository.apache.org/content/repositories/snapshots/org/apache/slider/slider-assembly/</p>
-<p>download the uploaded <code>.tar.gz</code>, expand it and verify that it is
complete. That includes</p>
+<div class="codehilite"><pre><span class="n">https</span><span
class="p">:</span><span class="o">//</span><span
class="n">repository</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">content</span><span class="o">/</span><span
class="n">repositories</span><span class="o">/</span><span
class="n">snapshots</span><span class="o">/</span><span
class="n">org</span><span class="o">/</span><span class="n">apache</span><span
class="o">/</span><span class="n">slider</span><span class="o">/</span><span
class="n">slider</span><span class="o">-</span><span
class="n">assembly</span><span class="o">/</span>
+</pre></div>
+
+
+<p>Download the uploaded <code>.tar.gz</code>, expand it and verify that it is
complete. That includes</p>
<ol>
<li>Verify that the file <code>slider-agent.tar.gz</code> exists.</li>
<li>Execute <code>bin/slider --version</code></li>
@@ -439,8 +458,11 @@ anyway.</p>
<ol>
-<li>This prompts for some version numbers: go with them unless you have
specific choices of
-versions.</li>
+<li>This prompts for the version numbers for the slider version to release: use
+ the <code>slider-0.60.0-incubating</code> or equivalent</li>
+<li>Use the same (as recommanded)
+go with them unless you have specific choices of
+versions. </li>
<li>Look at the output to verify the versions are what you want.</li>
<li>Roll back to the commit tagged earlier</li>
</ol>
@@ -452,42 +474,42 @@ versions.</li>
<ol>
-<li>the <code>release:prepare</code> command will trigger the local commit of
changes to POMs, tagging this and pushing up the branch.</li>
-<li>only skip those test runs if you have been running the tests in
advance.</li>
-<li>the funtests work by explicitly invoking <code>bin\slider</code> in the
expanded tar directory under
+<li>The <code>release:prepare</code> command will trigger the local commit of
changes to POMs, tagging this and pushing up the branch.</li>
+<li>Only skip those test runs if you have been running the tests in
advance.</li>
+<li>The funtests work by explicitly invoking <code>bin\slider</code> in the
expanded tar directory under
<code>../slider-assembly/target</code> âthat is, it doesn't download and
test any <code>.tar.gz</code> artifacts uploaded during
the staging process.</li>
</ol>
<p>You may be asked for your ASF git password repeatedly.
Consult <a
href="http://stackoverflow.com/questions/5343068/is-there-a-way-to-skip-password-typing-when-using-https-github";>StackOverflow</a></p>
<p><em>rolling back</em>
-After this phase (or when you cancel it), you'll need to roll back git, force
push the change to origin, and delete any newly created <code>slider-XY</code>
tag locally <em>and</em> remotely.</p>
+After this phase (or when you cancel it), you'll need to roll back git,</p>
+<h3 id="tip-reverting-changes">Tip: reverting changes</h3>
+<p>Try</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">release</span><span class="p">:</span><span class="n">rollback</span>
-<span class="n">mvn</span> <span class="n">clean</span>
</pre></div>
+<p>It <em>may</em> work. Then</p>
+<ol>
+<li>Via GUI/CLI Roll back the git branch to where it was before the release
actions started
+changing things. That should be the revision which you tagged.</li>
+<li>Force push that rolled back branch back to the git repository</li>
+<li>Delete any newly created <code>slider-XY-incubating</code> tag locally
<em>and</em> remotely.</li>
+<li>Run <code>mvn clean</code></li>
+</ol>
<p>If you are in a specific release-only directory (as per the
instructions):</p>
<div class="codehilite"><pre><span class="n">git</span> <span
class="n">clean</span> <span class="o">-</span><span class="n">d</span> <span
class="o">-</span><span class="n">f</span> <span class="o">-</span><span
class="n">x</span>
</pre></div>
<h3 id="tip-branching-instead-of-preparing">Tip: branching instead of
preparing</h3>
-<p>The <code>mvn release:branch</code> goal can be used instead of <code>mvn
release:prepare</code>, which creates a branch explicitly for the release. We
haven't used this yet.</p>
-<h3 id="tip-reverting-changes">Tip: reverting changes</h3>
-<p>Try</p>
-<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">release</span><span class="p">:</span><span class="n">rollback</span>
-</pre></div>
-
-
-<p>It <em>may</em> work. Also</p>
-<ol>
-<li>roll back the git branch to where it was before the release actions started
-changing things.</li>
-<li>Force push the rolled back branch back to the git repo.</li>
-</ol>
+<p>The <code>mvn release:branch</code> goal can be used instead of <code>mvn
release:prepare</code>,
+which creates a branch explicitly for the release. We haven't used this
yet.</p>
<h3 id="tip-validating-the-artifacts">Tip: Validating the artifacts</h3>
-<p>There's a small projects <a
href="https://github.com/steveloughran/slider-dependency-check";>slider-dependency-check</a>
which verifies that slider artifacts can be downloaded from the public or
staging repositories. Clone this project and read its instructions to verify
that everything went up to the staging repo.</p>
+<p>There's a small projects <a
href="https://github.com/steveloughran/slider-dependency-check";>slider-dependency-check</a>
+which verifies that slider artifacts can be downloaded from the public or
staging repositories.
+Clone this project and read its instructions to verify that everything went up
to the staging repo.</p>
<h2 id="close-the-release-in-nexus">Close the release in Nexus</h2>
<ol>
<li>log in to <a
href="https://repository.apache.org/index.html";>https://repository.apache.org/index.html</a>
@@ -612,7 +634,9 @@ http://pgp.mit.edu:11371/pks/lookup?op=v
</ol>
<p>Releasing "can take time", as the web site will inform you.</p>
<h2 id="publishing-the-source-and-binary-tarzip-files">Publishing the source
and binary tar/zip files</h2>
-<p>The ASF distribution system mirrors the source and binary files across the
all apache mirror sites. This the standard way which the archives are
distributed.</p>
+<p>The ASF distribution system mirrors the source and binary files across all
+apache mirror sites.</p>
+<p>This the standard way which the archives are distributed.</p>
<p>Publish the release as below:</p>
<h3 id="grab-the-released-artifacts-from-nexus">Grab the released artifacts
from Nexus</h3>
<ol>
@@ -658,7 +682,9 @@ are at the top of that file</p>
<p>The commit can take time. In the past it has been rejected due to the size
of
the patch...this has now been addressed and should remain so.</p>
<h3 id="web-site-updates">Web site updates</h3>
-<p>Update the Slider website as needed. Most of the documents would 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>
+<p>Update the Slider website as needed. Most of the documents would 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>
<p>The download details for the latest release needs to be updated after
mirrors are updated in . </p>
<p>Verify the download links at <a
href="http://slider.incubator.apache.org";>Slider Page</a>.</p>
<h2 id="announcing">Announcing</h2>
