svn commit: r868910 - in /websites/staging/rave/trunk/content: ./ release-process.html

[buildbot]

Author: buildbot
Date: Tue Jul  9 14:00:42 2013
New Revision: 868910

Log:
Staging update by buildbot for rave

Modified:
    websites/staging/rave/trunk/content/   (props changed)
    websites/staging/rave/trunk/content/release-process.html

Propchange: websites/staging/rave/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul  9 14:00:42 2013
@@ -1 +1 @@
-1501268
+1501269

Modified: websites/staging/rave/trunk/content/release-process.html
==============================================================================
--- websites/staging/rave/trunk/content/release-process.html (original)
+++ websites/staging/rave/trunk/content/release-process.html Tue Jul  9 
14:00:42 2013
@@ -370,7 +370,7 @@
 <p>You'll need to look at the output to ensure it contains only good 
signatures -</p>
 <p>gpg: Good signature from ...
 gpg: Signature made ...</p>
-<p><a name="combined" /></p>
+<p><a name="combined"></a></p>
 <h4 id="combined-release">Combined Release</h4>
 <p>In order to perform a combined release of the rave-master and rave-project 
trunks, do the following:    </p>
 <ul>
@@ -385,7 +385,7 @@ gpg: Signature made ...</p>
 </ul>
 </li>
 </ul>
-<p><a name="scripted" /></p>
+<p><a name="scripted"></a></p>
 <h4 id="scripted-release">Scripted Release</h4>
 <p>There are two scripts in the repository created to facilitate simpler 
releases:  release.sh &amp; publish.sh.  The release script handles steps up to 
the VOTE e-mails and the publish script handles publishing the artifacts to the 
mirrors once a successful vote has been achieved.  </p>
 <p>To use the scripts, do the following:</p>