mahout-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r971505 - in /websites/staging/mahout/trunk/content: ./ developers/how-to-release.html
Date Fri, 06 Nov 2015 01:19:05 GMT
Author: buildbot
Date: Fri Nov  6 01:19:05 2015
New Revision: 971505

Staging update by buildbot for mahout

    websites/staging/mahout/trunk/content/   (props changed)

Propchange: websites/staging/mahout/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov  6 01:19:05 2015
@@ -1 +1 @@

Modified: websites/staging/mahout/trunk/content/developers/how-to-release.html
--- websites/staging/mahout/trunk/content/developers/how-to-release.html (original)
+++ websites/staging/mahout/trunk/content/developers/how-to-release.html Fri Nov  6 01:19:05
@@ -263,11 +263,22 @@
   <div id="content-wrap" class="clearfix">
    <div id="main">
-    <h1 id="how-to-release-mahout">How To Release Mahout</h1>
+    <style type="text/css">
+/* The following code is added by
+   It was originally lifted from */
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<h1 id="how-to-release-mahout">How To Release Mahout<a class="headerlink" href="#how-to-release-mahout"
title="Permanent link">&para;</a></h1>
 <p><em>This page is prepared for Mahout committers. You need committer rights
 create a new Mahout release.</em></p>
 <p><a name="HowToRelease-ReleasePlanning"></a></p>
-<h1 id="release-planning">Release Planning</h1>
+<h1 id="release-planning">Release Planning<a class="headerlink" href="#release-planning"
title="Permanent link">&para;</a></h1>
 <p>Start a discussion on mahout-dev about having a release, questions to bring
 up include:</p>
@@ -282,7 +293,7 @@ commit to having time to help test the r
 <p><a name="HowToRelease-CodeFreeze"></a></p>
-<h1 id="code-freeze">Code Freeze</h1>
+<h1 id="code-freeze">Code Freeze<a class="headerlink" href="#code-freeze" title="Permanent
 <p>For 7-14 days prior to the release target date, have a "code freeze" where
 committers agree to only commit things if they:</p>
@@ -293,9 +304,9 @@ warnings)</li>
 <li>Are new tests and bug fixes for new bugs encountered by manually testing</li>
 <p><a name="HowToRelease-StepsForReleaseEngineer"></a></p>
-<h1 id="steps-for-release-engineer">Steps For Release Engineer</h1>
+<h1 id="steps-for-release-engineer">Steps For Release Engineer<a class="headerlink"
href="#steps-for-release-engineer" title="Permanent link">&para;</a></h1>
 <p><a name="HowToRelease-Beforebuildingrelease"></a></p>
-<h2 id="before-building-release">Before building release</h2>
+<h2 id="before-building-release">Before building release<a class="headerlink" href="#before-building-release"
title="Permanent link">&para;</a></h2>
 <li>Check that all tests pass after a clean compile: mvn clean test</li>
 <li>Check that there are no remaining unresolved Jira issues with the
@@ -303,15 +314,15 @@ upcoming version number listed as the "F
 <li>Publish any prev. unpublished Third Party Deps: <a href="thirdparty-dependencies.html">Thirdparty
 <p><a name="HowToRelease-PreviewingtheArtifacts"></a></p>
-<h2 id="previewing-the-artifacts">Previewing the Artifacts</h2>
+<h2 id="previewing-the-artifacts">Previewing the Artifacts<a class="headerlink"
href="#previewing-the-artifacts" title="Permanent link">&para;</a></h2>
 <li>To build the artifacts:</li>
-<h1 id="mvn-pmahout-releaseapache-releasehadoop2-package">mvn -Pmahout-release,apache-release,hadoop2
+<h1 id="mvn-pmahout-releaseapache-releasehadoop2-package">mvn -Pmahout-release,apache-release,hadoop2
package<a class="headerlink" href="#mvn-pmahout-releaseapache-releasehadoop2-package" title="Permanent
 <p><a name="HowToRelease-Makingarelease"></a></p>
-<h2 id="making-a-release">Making a release</h2>
+<h2 id="making-a-release">Making a release<a class="headerlink" href="#making-a-release"
title="Permanent link">&para;</a></h2>
 <li>Check if documentation needs an update</li>
 <li>Update the web site's news by updating a working copy of the SVN
@@ -320,10 +331,11 @@ directory at
 that it is reflected in the copy of the website included with the release
 for documentation purposes.</li>
 <li>If this is your first release, add your key to the KEYS file. The KEYS
-file is located in Subversion at
- and copy it
-to the release directory. Make sure you commit your change.  See
+file is located on Github at
+ and copy it
+to the release directory. 
+Make sure you commit your change.
 <li>Ensure you have set up standard Apache committer settings in
  ~/.m2/settings.xml as per <a href="">this
@@ -369,43 +381,63 @@ then immediately access, but, there is a
 minute to the non-US servers. To temporarily force using the US-based
 server, edit your equivalent of /etc/hosts and map the IP address of to</li>
-<li>Create the release candidate: {{mvn -Pmahout_release release:prepare release:perform}}.
If you have problems authenticating to, try adding to the command line {{-Dusername=[user]
- -Dpassword=[password]}}. If it screws up, do not clean or release:clean
-without first trying to do: release:rollback.  This will likely save you
-time and do the right thing.  If it doesn't work, then do clean and
-release:clean and also delete the tag from svn, if it was created. You may
-also have to rollback the version numbers in the POM files.
-    ( If you want to skip test cases while rebuilding, use mvn
--DpreparationGoals="clean compile" release:prepare release:perform)</li>
-<li>Review the artifacts, etc. on the Apache Repository (using Sonatype's
+<p>Create the release candidate:</p>
+<p>mvn -Pmahout-release,apache-release,hadoop2 release:prepare release:perform}}. </p>
+<p>If you have problems authenticating to, try adding to the command
line </p>
+<div class="codehilite"><pre>  <span class="o">-</span><span class="n">Dusername</span><span
class="p">=</span><span class="o">\</span><span class="p">[</span><span
class="n">user</span><span class="p">]</span><span class="o">\</span>
<span class="o">-</span><span class="n">Dpassword</span><span class="p">=</span><span
class="o">\</span><span class="p">[</span><span class="n">password</span><span
class="o">\</span><span class="p">]</span>
+<p>If it screws up, first try doing:</p>
+<p>mvn -Dmahout-release,apache-release,hadoop2 release:rollback. </p>
+<p>followed by</p>
+<p>mvn -Dmahout-release,apache-release,hadoop2 release:clean</p>
+<p>This will likely save you time and do the right thing. </p>
+<p>You may also have to rollback the version numbers in the POM files.</p>
+<div class="codehilite"><pre><span class="p">(</span> <span class="n">If</span>
<span class="n">you</span> <span class="n">want</span> <span class="n">to</span>
<span class="n">skip</span> <span class="n">test</span> <span class="n">cases</span>
<span class="k">while</span> <span class="n">rebuilding</span><span
class="p">,</span> <span class="n">use</span> <span class="n">mvn</span>
+<p>-DpreparationGoals="clean compile" release:prepare release:perform)
+<em> Review the artifacts, etc. on the Apache Repository (using Sonatype's
 Nexus application) site:
            You will need to login using your ASF SVN credentials and then
-browse to the staging area.</li>
-<li>Once you have reviewed the artifacts, you will need to "Close" out
+browse to the staging area.
+</em> Once you have reviewed the artifacts, you will need to "Close" out
 the staging area under Nexus, which then makes the artifacts available for
-others to see.<ul>
-<li>Log in to Nexus</li>
-<li>Click the Staging Repositories link in the left hand menu</li>
-<li>Click the Mahout staged one that was just uploaded by the
-release:perform target</li>
-<li>Click Close in the toolbar. See
+others to see.
+     * Log in to Nexus
+     * Click the Staging Repositories link in the left hand menu
+     * Click the Mahout staged one that was just uploaded by the
+release:perform target
+     * Click Close in the toolbar. See
-for a picture</li>
-<li>Copy the "Repository URL" link to your email; it should be like
-<li>Call a VOTE on  Votes require 3 days before
+for a picture
+     * Copy the "Repository URL" link to your email; it should be like
+<em> Call a VOTE on  Votes require 3 days before
 passing.  See Apache [release policy|]
- for more info.</li>
-<li>If there's a problem, you need to unwind the release and start all
+ for more info.
+</em> If there's a problem, you need to unwind the release and start all
-        mvn -Pmahout_release versions:set -DnewVersion=PREVIOUS_SNAPSHOT
-        mvn -Pmahout_release versions:commit
-        svn commit 
-        svn rm
-        </blockquote></li>
+        mvn -Pmahout-release,apache-release,hadoop2 versions:set -DnewVersion=PREVIOUS_SNAPSHOT</p>
+<div class="codehilite"><pre>    mvn -Pmahout-release,apache-release,hadoop2
+    git commit
+    git push --delete apache <span class="nt">&lt;tagname&gt;</span>
(deletes the remote tag)
+    git tag -d tagname (deletes the local tag)
+    <span class="nt">&lt;/blockquote&gt;</span>
 <li>Release the artifact in the Nexus Repository in the same way you
 Closed it earlier.</li>
 <li>Add your key to the KEYS file at
@@ -445,18 +477,18 @@</li>
-<h2 id="post-release">Post Release</h2>
-<h3 id="versioning">Versioning</h3>
+<h2 id="post-release">Post Release<a class="headerlink" href="#post-release" title="Permanent
+<h3 id="versioning">Versioning<a class="headerlink" href="#versioning" title="Permanent
 <li>Create the next version in JIRA (if it doesn't already exist)   </li>
 <li>Mark the version as "released" in JIRA (noting the release date)</li>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation"
title="Permanent link">&para;</a></h3>
 <li>Change wiki to match current best practices (remove/change deprecations,
-<h3 id="publicity">Publicity</h3>
+<h3 id="publicity">Publicity<a class="headerlink" href="#publicity" title="Permanent
 <li>update freshmeat</li>
 <li>!TheServerSide blurb</li>
@@ -464,12 +496,12 @@ etc)</li>
 <li>Update MLOSS entry:  See Grant for
-<h2 id="related-resources">Related Resources</h2>
+<h2 id="related-resources">Related Resources<a class="headerlink" href="#related-resources"
title="Permanent link">&para;</a></h2>
-<h1 id="todo-things-to-cleanup-in-this-document">TODO: Things To Cleanup in this document</h1>
+<h1 id="todo-things-to-cleanup-in-this-document">TODO: Things To Cleanup in this document<a
class="headerlink" href="#todo-things-to-cleanup-in-this-document" title="Permanent link">&para;</a></h1>
 <li>more specifics about things to test before starting or after packaging
 (RAT, run scripts against example, etc...)</li>

View raw message