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

[buildbot]

Author: buildbot
Date: Sat Mar 16 06:28:56 2013
New Revision: 854702

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 Sat Mar 16 06:28:56 2013
@@ -1 +1 @@
-1457207
+1457209

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 Sat Mar 16 
06:28:56 2013
@@ -173,6 +173,13 @@
        The instructions provided here are consistent with, but not a 
replacement for
        the <a class="externalLink" 
href="http://www.apache.org/dev/release.html";>ASF Release Guidlines.</a> 
        </p>
+    <p>Commons uses the Nexus installation at the Apache Software Foundation 
to stage Maven artifacts
+    before the release and later publish them, the Commons Parent POM contains 
all the necessary configuration.
+    This guide covers deploying to Nexus using Maven, for alternatives see
+    <a class="externalLink" 
href="http://www.apache.org/dev/publishing-maven-artifacts.html";>the ASF wide 
documentation</a>.
+    If this is the first time you are publishing to the ASF's Nexus instance
+    you'll need to <a class="externalLink" 
href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env";>prepare
+    your development environment</a>.</p>
     <p>
     The examples below assume that preparation is being made to release 
version <i>1.2</i>
     of component <i>Foo</i>.
@@ -183,7 +190,7 @@
     Commons components are expected to use Maven to build the project website. 
Components
     may choose to use either Maven or Ant to build the actual jar and tar/zip 
files to be distributed,
     although it is recommended that Maven be used for this. Both approaches 
are covered
-    below.  The version of Maven used is assumed to be Maven 2 throughout.  At 
a minimum, Commons
+    below.  The version of Maven used is assumed to be Maven 3 throughout.  At 
a minimum, Commons
     releases <b>must</b> include full source distributions packaged in tar and 
zip
     archives.
     </p>
@@ -312,7 +319,9 @@
       &lt;properties&gt;
         &lt;commons.componentid&gt;foo&lt;/commons.componentid&gt;
         &lt;commons.release.version&gt;1.2&lt;/commons.release.version&gt;
-        &lt;commons.binary.suffix&gt;&lt;/commons.binary.suffix&gt;
+        &lt;commons.rc.version&gt;RC1&lt;/commons.rc.version&gt;
+
+        &lt;-- properties not related to versioning --&gt;
         &lt;commons.jira.id&gt;FOO&lt;/commons.jira.id&gt;
         &lt;commons.jira.pid&gt;007&lt;/commons.jira.pid&gt;
         &lt;maven.compile.source&gt;1.3&lt;/maven.compile.source&gt;