svn commit: r937418 - in /websites/staging/commons/trunk/content: ./ releases/prepare.html

[bu...@apache.org]

Author: buildbot
Date: Fri Jan 23 15:17:22 2015
New Revision: 937418

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 Fri Jan 23 15:17:22 2015
@@ -1 +1 @@
-1654230
+1654233

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 Fri Jan 23 15:17:22 2015
@@ -926,13 +926,13 @@
       </p>
 <div>
 <pre>
-        mvn deploy -Prelease [-Pjava-1.x]
+        mvn deploy -Prelease -Duser.name=&lt;your apache ID&gt; [-Pjava-1.x]
       </pre></div>
-      If you want to do a test deployment first, you can add the following option:
+      If you want to do a test deployment first, you can add the following options:
       
 <div>
 <pre>
-        mvn deploy -Prelease -Ptest-deploy [-Pjava-1.x]
+        mvn deploy -Prelease -Duser.name=&lt;your apache ID&gt; -Ptest-deploy [-Pjava-1.x] [-Dgpg.skip]
       </pre></div>
       The &quot;test-deploy&quot; profile uploads the artifacts to target/deploy instead of Nexus so one can check all the required files
       have been created with the expected contents.