Author: buildbot
Date: Wed Feb 4 15:35:06 2015
New Revision: 938967
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 4 15:35:06 2015
@@ -1 +1 @@
-1656975
+1657287
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 4
15:35:06 2015
@@ -339,11 +339,13 @@ finalizing the release notes.</p>
<h1 id="automated-releases-via-maven">Automated releases via maven</h1>
<p>The Slider project uses Maven to automatically publish all the slider
artifacts âsource and binaryâ to the ASF repositories</p>
-<p>Core sequence
-1. Dry Run
-1. Deploy to staging
-1. Publish the real release
-1. Get the votes in</p>
+<p>Core sequence</p>
+<ol>
+<li>Dry Run</li>
+<li>Deploy to staging</li>
+<li>Publish the real release</li>
+<li>Get the votes in</li>
+</ol>
<p>If the vote fails: fix the issues then repeat</p>
<p>Recommended Reading</p>
<ul>
@@ -498,6 +500,24 @@ with your ASF username & LDAP passwo
<li>Wait for the close process to complete.</li>
<li>Get the URL of the closed staging repository. This is needed for the next
step âthe votes.</li>
</ol>
+<h2 id="tell-jira-of-the-releases">Tell JIRA of the releases</h2>
+<p>Tell JIRA there's a new release. This moves it from "unreleased" to
"released", creating a URL listing all issues fixed. </p>
+<p>This URL can be used in the vote emails to highlight changes.</p>
+<p><em>Important:</em> To perform this task, you must be registered as an
admin for the
+Slider project on JIRA.</p>
+<ol>
+<li>Go to the <a
href="https://issues.apache.org/jira/plugins/servlet/project-config/SLIDER/versions">Slider
Versions page</a></li>
+<li>Locate the pending release. Make sure it is in the correct order of
releases: all previous releases MUST be below it; future releases above it. The
immediate next release MUST be directly above the pending release.</li>
+<li>On the pending release
+ i. Set the release date to the current day.
+ i. Select the drop down "gear-cog" menu to the right of the page, then
the "Release" option.
+ i. Carrying all forward issues that haven't been completed *except the
JIRA covering the release itself.</li>
+<li>Go to the <a
href="https://issues.apache.org/jira/browse/SLIDER/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel">Slider
versions page</a></li>
+<li>Locate the release just issued and click through it.</li>
+<li>Get the page link</li>
+<li>Ideally, shorten it via the <a href="https://s.apache.org/">ASF Link
shortener</a></li>
+</ol>
+<p>If the vote is cancelled, the release can be "unreleased". </p>
<h2 id="get-the-votes-in">Get the Votes In</h2>
<h3 id="set-up-your-env-vars-for-email-templates">Set up your env vars for
email templates</h3>
<p>set up the environment with the git release tag, URL to the staging
repository, and your ASF username:</p>
@@ -514,7 +534,7 @@ with your ASF username & LDAP passwo
</pre></div>
-<h3 id="call-for-a-slider-vote">Call for a slider vote</h3>
+<h3 id="call-for-a-release-vote-on-the-devslider-list">Call for a release vote
on the dev@slider list</h3>
<p>Call for a release VOTE to the dev mailing list
(<code>[email protected]</code>).</p>
<p>To build the URLs, echo them then verify in your browser that they are
present</p>
<p>echo "[VOTE] Apache Slider Incubating Release $SLIDER_RELEASE"</p>
@@ -531,14 +551,48 @@ echo "PGP keys at http://pgp.mit.edu:113
<ul>
<li>CHECK ALL THE URLS *</li>
</ul>
+<h3 id="wait-for-the-devslider-result">Wait for the dev@slider result</h3>
+<p>When it comes in, post the results in another email.</p>
<h3 id="call-for-an-incubator-vote">Call for an incubator vote</h3>
-<p>If the VOTE passes, call for VOTE from IPMC. Include the VOTE and RESULT
thread from the dev alias.
-If that VOTE passes with the IPMC send a RESULT mail.</p>
+<p>If the VOTE passes, call for (the binding) VOTE from IPMC. Include the VOTE
and RESULT threads from the developer mailing list.</p>
+<ol>
+<li>Go to the <a
href="http://mail-archives.apache.org/mod_mbox/incubator-slider-dev/">Slider
mail archives</a>.</li>
+<li>Locate the email thread of the vote
+ i. get the permanent link to the email at the start of the vote
+ i. shorten it via the <a href="https://s.apache.org/">ASF Link
Shortener</a>. You must be signed in with your ASF LDAP password.
+ i. Use this as the URL for the voting thread</li>
+<li>Repeat for the email of the results</li>
+</ol>
+<p>[VOTE] Release Apache Slider 0.61.0-incubating</p>
+<p>Hi all, </p>
+<p>This is to call for a vote for releasing slider-0.61.0-incubating. </p>
+<p>This is a source+binary release, with the same actual source as the
previous slider-0.60.0-incubating release. We've done this for downstream
projects;
+once the release process is successfully reworked we'll use it in future
+"feature" releases.</p>
+<p>Summary of fixes in this release
+http://s.apache.org/7rQ</p>
+<p>Artifacts at
+https://repository.apache.org/content/repositories/orgapacheslider-1003/</p>
+<p>Git source tag:
+https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=commit;h=64a8bac068e6801748fb973dbfb590bc62c60935</p>
+<p>PGP keys at
+http://pgp.mit.edu:11371/pks/lookup?op=vindex&[email protected]</p>
+<p>Vote thread : http://s.apache.org/Xpd</p>
+<p>Results : http://s.apache.org/AsJ</p>
+<p>Please vote on releasing this package as Apache Slider 0.61.0-incubating
</p>
+<p>The vote will be open for 72 hours. </p>
+<p>[ ] +1 Release this package
+[ ] +0 no opinion
+[ ] -1 Do not release this package because ... </p>
+<p>Thanks, </p>
+<p>The Apache Slider Team </p>
+<h3 id="await-the-generalincubator-results-publish-them">Await the
general@incubator results; publish them</h3>
+<p>After 72 hours, publish the results</p>
<p>Sample:</p>
<div class="codehilite"><pre><span class="n">Title</span><span
class="p">:</span> <span class="p">[</span><span class="n">RESULT</span><span
class="p">][</span><span class="n">VOTE</span><span class="p">]</span> <span
class="n">Apache</span> <span class="n">Slider</span> $<span
class="n">SLIDER_RELEASE</span> $<span class="n">RELEASE_RC</span>
<span class="n">Thanks</span> <span class="k">for</span> <span
class="n">the</span> <span class="n">votes</span><span class="p">.</span>
-<span class="n">The</span> <span class="n">VOTE</span> <span
class="n">passes</span> <span class="n">with</span> 5<span class="p">,</span>
<span class="o">+</span>1 <span class="n">votes</span> <span
class="n">from</span> <span class="n">IPMC</span><span class="p">.</span>
+<span class="n">The</span> <span class="n">VOTE</span> <span
class="n">passes</span> <span class="n">with</span> <span
class="n">X</span><span class="p">,</span> <span class="o">+</span>1 <span
class="n">votes</span> <span class="n">from</span> <span
class="n">IPMC</span><span class="p">.</span>
<span class="n">List</span> <span class="n">any</span> <span
class="n">IPMC</span> <span class="n">votes</span><span class="p">.</span>
@@ -548,6 +602,7 @@ If that VOTE passes with the IPMC send a
</pre></div>
+<p>If the vote has been successful âyou may now release the artifacts.</p>
<h2 id="publishing-the-nexus-staging-repository">Publishing the Nexus staging
repository</h2>
<p>Once âand only onceâ the incubator vote is successful, you may release
the nexus-staged artifacts.</p>
<ol>
@@ -599,16 +654,15 @@ are at the top of that file</p>
</pre></div>
-<p><strong>Step 14</strong></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>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>
<p>Send an announcement:</p>
-<p>The bits published in <strong>Step 13</strong> may take up to 24 hours to
replicate to the mirrors.</p>
-<p>Send an announcement to the Slider dev, Slider user, and the general Apache
announcement ([email protected]) list after the bits have replicated.
-To send the message to [email protected], you will need to send the
message from your apache.org email address.</p>
+<p>The released artifacts may take up to 24 hours to replicate to the
mirrors.</p>
+<p>Send an announcement to the Slider dev, Slider user, and the general Apache
announcement (<code>[email protected]</code>) list after the bits have
replicated.
+To send the message to <code>[email protected]</code>, you will need to
send the message from your <code>apache.org</code> email address.</p>
<p>Sample:</p>
<div class="codehilite"><pre><span class="n">Title</span><span
class="p">:</span> <span class="p">[</span><span class="n">ANNOUNCE</span><span
class="p">]</span> <span class="n">Apache</span> <span class="n">Slider</span>
<span class="n">x</span><span class="p">.</span><span class="n">y</span><span
class="p">.</span><span class="n">z</span><span class="o">-</span><span
class="n">incubating</span><span class="p">.</span>
@@ -640,12 +694,6 @@ To send the message to announcement@apac
<h2 id="finish-the-jira">Finish the JIRA</h2>
<p>Log the time, close the issue. This should normally be the end of a
sprint âso wrap that up too.</p>
-<h2 id="updating-jira-releases">Updating JIRA Releases</h2>
-<p>Tell JIRA there's a new release. You must be registered as an admin for the
-Slider project on JIRA.</p>
-<p>Go to the <a
href="https://issues.apache.org/jira/plugins/servlet/project-config/SLIDER/versions">Slider
Versions page</a></p>
-<p>Release the version you've done, carrying forward issues that haven't been
done
-yet.</p>
<h2 id="get-back-to-developing">Get back to developing!</h2>
<p>Check out the develop branch and purge all release artifacts</p>
<div class="codehilite"><pre><span class="n">git</span> <span
class="n">checkout</span> <span class="n">develop</span>