commons-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r977118 - in /websites/staging/commons/trunk/content: ./ releases/prepare.html
Date Tue, 05 Jan 2016 20:16:42 GMT
Author: buildbot
Date: Tue Jan  5 20:16:41 2016
New Revision: 977118

Log:
Staging update by buildbot for commons

Modified:
    websites/staging/commons/trunk/content/   (props changed)
    websites/staging/commons/trunk/content/releases/prepare.html

Propchange: websites/staging/commons/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jan  5 20:16:41 2016
@@ -1 +1 @@
-1723128
+1723154

Modified: websites/staging/commons/trunk/content/releases/prepare.html
==============================================================================
--- websites/staging/commons/trunk/content/releases/prepare.html (original)
+++ websites/staging/commons/trunk/content/releases/prepare.html Tue Jan  5 20:16:41 2016
@@ -1010,7 +1010,9 @@
         distribution <tt>.tar.gz</tt> and <tt>.zip</tt> files are
there as well.  Before you
         <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage">close</a>
the staging
         repository you must remove the tarballs/zips together with their PGP signatures and
checksums using
-        the Nexus web interface.</p>
+        the Nexus web interface.  While
+        you are at it you can also remove the checksums Nexus created for the PGP signatures
of the
+        remaining artifacts, they are not needed at all.</p>
       
 <p><i>If anybody knows how we can avoid uploading the distributions, please lend
a hand.  The manual step is
         not only annoying, uploading the files also wastes time and bandwidth.</i></p>



Mime
View raw message