svn commit: r832366 - in /websites/staging/bval/trunk/content: ./ release-process.html

[bu...@apache.org]

Author: buildbot
Date: Tue Sep 18 16:41:10 2012
New Revision: 832366

Log:
Staging update by buildbot for bval

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

Propchange: websites/staging/bval/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 18 16:41:10 2012
@@ -1 +1 @@
-1386791
+1387242

Modified: websites/staging/bval/trunk/content/release-process.html
==============================================================================
--- websites/staging/bval/trunk/content/release-process.html (original)
+++ websites/staging/bval/trunk/content/release-process.html Tue Sep 18 16:41:10 2012
@@ -388,6 +388,9 @@ site:deploy</code> and will deploy the s
  <code>sources</code>, and <code>tests</code> jars, as well as <code>pom</code>s, ... have <code>.asc</code> (GPG signature) and <code>.md5</code>
  files (see <a href="http://people.apache.org/~henkp/repo/faq.html">Repository FAQ</a> and <a href="http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig">Detached Signatures</a>). The <code>source-release.zip</code> of <code>bval-parent</code>
  should likewise have signature and checksum files.</li>
+<li><em>Optional:</em> It's nice at this point to delete the "signature checksum" files from the staging repo:
+ <code>*.asc.sha1</code> <code>*.asc.md5</code>. If you choose to do so, proceed carefully as you don't want to delete
+ the wrong ones.</li>
 </ol>
 </li>
 <li>Close the nexus staging repo:<ol>