svn commit: r977430 - in /websites/staging/accumulo/trunk/content: ./ releasing.html

[bu...@apache.org]

Author: buildbot
Date: Sun Jan 10 18:32:08 2016
New Revision: 977430

Log:
Staging update by buildbot for accumulo

Modified:
    websites/staging/accumulo/trunk/content/   (props changed)
    websites/staging/accumulo/trunk/content/releasing.html

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Jan 10 18:32:08 2016
@@ -1 +1 @@
-1722957
+1723944

Modified: websites/staging/accumulo/trunk/content/releasing.html
==============================================================================
--- websites/staging/accumulo/trunk/content/releasing.html (original)
+++ websites/staging/accumulo/trunk/content/releasing.html Sun Jan 10 18:32:08 2016
@@ -282,9 +282,15 @@ will make it publicly available for othe
 list</a> and get the ball rolling. If the vote ultimately fails, you delete
 the staged repository, clean up the branch you created (or wait until the release ultimately passes if you
 choose), and fix what needs fixing.</p>
-<p>If the vote passes, huzzah, you're almost done. All you need to do is to promote that stage repository
-using Nexus which you can do with the click of a button. This will trigger a process to get the release
-out to all of the mirrors.</p>
+<p>If the vote passes, huzzah, you're almost done.</p>
+<h2 id="promote-the-artifacts">Promote the artifacts<a class="headerlink" href="#promote-the-artifacts" title="Permanent link">&para;</a></h2>
+<p>Promote that staged repository using Nexus which you can do with the click of a button. This will trigger
+a process to get the release out to all of the mirrors.</p>
+<h2 id="create-the-final-git-tag">Create the final Git tag<a class="headerlink" href="#create-the-final-git-tag" title="Permanent link">&para;</a></h2>
+<p>The Git repository should also contain a tag which refers to the final commit which made up a release. This tag
+should also be signed with your GPG key. To ensure proper retention on release (stemming from ASF policy
+requirements), This final tag <em>must</em> being with "rel/". For example, a release of 1.7.0 should have a corresponding
+tag name of "rel/1.7.0".</p>
 <h2 id="copy-artifacts-to-distapacheorg">Copy artifacts to dist.apache.org<a class="headerlink" href="#copy-artifacts-to-distapacheorg" title="Permanent link">&para;</a></h2>
 <p>An SVN server is running at https://dist.apache.org/repos/dist/release/accumulo. You need to upload the release
 tarballs, the GPG signatures and checksum files to the correct directory (based on the release number). If you