svn commit: r1723944 - /accumulo/site/trunk/content/releasing.mdtext

[el...@apache.org]

Author: elserj
Date: Sun Jan 10 18:31:54 2016
New Revision: 1723944

URL: http://svn.apache.org/viewvc?rev=1723944&view=rev
Log:
Hullo? Buildbot?

Modified:
    accumulo/site/trunk/content/releasing.mdtext

Modified: accumulo/site/trunk/content/releasing.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/releasing.mdtext?rev=1723944&r1=1723943&r2=1723944&view=diff
==============================================================================
--- accumulo/site/trunk/content/releasing.mdtext (original)
+++ accumulo/site/trunk/content/releasing.mdtext Sun Jan 10 18:31:54 2016
@@ -85,9 +85,20 @@ list](mailto:dev@accumulo.apache.org) an
 the staged repository, clean up the branch you created (or wait until the release ultimately passes if you
 choose), and fix what needs fixing.
 
-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.
+If the vote passes, huzzah, you're almost done.
+
+## Promote the artifacts 
+
+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.
+
+## Create the final Git tag
+
+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 *must* being with "rel/". For example, a release of 1.7.0 should have a corresponding
+tag name of "rel/1.7.0".
+
 
 ## Copy artifacts to dist.apache.org