svn commit: r936338 - in /websites/staging/slider/trunk/content: ./ developing/releasing.html

[bu...@apache.org]

Author: buildbot
Date: Thu Jan 15 17:34:48 2015
New Revision: 936338

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 Thu Jan 15 17:34:48 2015
@@ -1 +1 @@
-1651393
+1652185

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 Thu Jan 15 17:34:48 2015
@@ -222,7 +222,7 @@ starting to make a release</em></p>
 <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>
 <p>e.g. <code>mvn clean install -DskipTests -Prelease-2.6</code></p>
-<h2 id="wzxhzdk44wzxhzdk45phase-i"><a name="phase1"></a>Phase - I</h2>
+<h2 id="wzxhzdk45wzxhzdk46phase-i"><a name="phase1"></a>Phase - I</h2>
 <p><strong>Step #0:</strong> Sync up with the ASF repo. You do not want to release the wrong
 code.</p>
 <div class="codehilite"><pre><span class="n">git</span> <span class="n">checkout</span> <span class="n">develop</span>
@@ -355,7 +355,7 @@ sprint -so wrap that up too.</p>
 
 
 <p><em>At this point you are ready for Apache release from master.</em></p>
-<h2 id="wzxhzdk46wzxhzdk47phase-ii-publish-to-the-asf"><a name="phase2"></a>Phase - II: publish to the ASF</h2>
+<h2 id="wzxhzdk47wzxhzdk48phase-ii-publish-to-the-asf"><a name="phase2"></a>Phase - II: publish to the ASF</h2>
 <p>This phase of the process creates the artifacts for the ASF.
 This is done in a separate directory to ensure that nothing accidentally gets in.</p>
 <p>Preamble: set up the RC Version </p>
@@ -692,12 +692,24 @@ the actual development version.</p>
 
 
 <h2 id="uploading-for-a-vote">uploading for a vote</h2>
-<p>mvn release:clean
-  mvn release:prepare -DautoVersionSubmodules=true -Darguments="-DskipTests -DskipITs" -Dresume=false
-  mvn release:perform </p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">release</span><span class="p">:</span><span class="n">clean</span>
+<span class="n">mvn</span> <span class="n">release</span><span class="p">:</span><span class="n">prepare</span> <span class="o">-</span><span class="n">DautoVersionSubmodules</span><span class="p">=</span><span class="n">true</span> <span class="o">-</span><span class="n">Darguments</span><span class="p">=</span>&quot;<span class="o">-</span><span class="n">DskipTests</span> <span class="o">-</span><span class="n">DskipITs</span>&quot; <span class="o">-</span><span class="n">Dresume</span><span class="p">=</span><span class="n">false</span>
+<span class="n">mvn</span> <span class="n">release</span><span class="p">:</span><span class="n">perform</span>
+</pre></div>
+
+
+<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>
 <h3 id="closing-the-release">Closing the release</h3>
 <p>log in to <a href="https://repository.apache.org/index.html">https://repository.apache.org/index.html</a>
 with your ASF username &amp; LDAP password</p>
+<h3 id="reverting">reverting</h3>
+<p>Try
+    mvn release:rollback</p>
+<p>It <em>may</em> work. Also
+1. roll back the git branch to where it was before the release actions started
+changing things.
+1. Force push the rolled back branch back to the git repo.</p>
 <h1 id="notes-on-a-changed-process">Notes on a changed process</h1>
 <p>This is some working notes on the 0.61 release</p>
 <ul>