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

[buildbot]

Author: buildbot
Date: Fri Jun  7 23:09:01 2013
New Revision: 864774

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 Jun  7 23:09:01 2013
@@ -1 +1 @@
-1490862
+1490863

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 Jun  7 
23:09:01 2013
@@ -713,10 +713,15 @@
 
     <div class="section"><h3>Create the Release Candidate Website<a 
name="Create_the_Release_Candidate_Website"></a></h3>
     <p>
-       The new website should be published in your home directory on 
people.apache.org. If using Maven, 
-    run &quot;mvn site&quot; locally, tar or zip the site in target/ and scp 
and unpack the files
+       The new website should be published in your home directory on 
people.apache.org.
+    For example:
+    </p><div><pre>
+      mvn site [-Pjacoco] [-Pcobertura]
+    </pre></div>
+     The optional &quot;jacoco&quot; and &quot;cobertura&quot; profiles are 
used to select the appropriate code coverage tool if required.
+     Then tar or zip the site in target/site and scp and unpack the files
       on people.apache.org in a directory <tt>~/public_html/foo-1.2-RC1</tt>.
-       </p>
+       
        <p>
        Note that when verifying this candidate site you need to be careful of 
absolute
        URLs; following these will lead to the currently published site, not to 
the