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

[buildbot]

Author: buildbot
Date: Thu Apr 19 14:49:05 2018
New Revision: 1028668

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 Thu Apr 19 14:49:05 2018
@@ -1 +1 @@
-1829536
+1829549

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 Thu Apr 19 
14:49:05 2018
@@ -1003,9 +1003,46 @@ mvn versions:display-plugin-updates -U</
       <i>TODO:</i> Does the Maven Release plugin work with git?
 
     </div></div>
+
+    
+<div class="section">
+<h3><a 
name="Create_the_Release_Candidate_with_the_Commons_Release_Plugin."></a>Create 
the Release Candidate with the Commons Release Plugin.</h3>
+      The <a href="commons-release-plugin/index.html">Commons Release 
Plugin</a>, as of
+      commons-parent-46 is included but disabled. Note, as of version 1.2 of 
the plugin and version
+      46 of the parent, we have throughly tested single module builds, but 
multi-module builds remain
+      an open problem (which may work, but at the time of writing have not 
been fully vetted). To
+      enable the plugin, one needs to configure the <tt>properties</tt> 
section of the pom as follows:
+      
+<div>
+<pre class="prettyprint">
+&lt;properties&gt;
+    
&lt;commons.release.isDistModule&gt;true&lt;/commons.release.isDistModule&gt;
+    
&lt;commons.distSvnStagingUrl&gt;scm:svn:https://dist.apache.org/repos/dist/dev/commons/foo&lt;/commons.distSvnStagingUrl&gt;
+&lt;/properties&gt;</pre></div>
+      where <tt>foo</tt> represents our component. Furthermore, during a 
release build, we ask that the svn
+      folder be empty. We then generate our release build by runnning:
+      
+<div>
+<pre>
+        mvn -Duser.name=${my_apache_id} -Prelease -Ptest-deploy clean package 
site deploy</pre></div>
+      to test our deployment. Note, all of the staged items end up in
+      <tt>target/commons-release-plugin/scm</tt>. And, to perform a full 
release, we run:
+      
+<div>
+<pre>
+        mvn -Duser.name=${my_apache_id} -Prelease clean package site 
deploy</pre></div>
+      Using the release plugin should build and stage the non-assembly built 
artifacts to Nexus, and stage
+      the assemblies to the svn location along with the site and the 
<tt>RELEASE-NOTES.txt</tt> from the
+      root of the project.
+
+      After finishing the build you will need to &quot;close&quot; the staging 
repository in the
+      <a class="externalLink" href="https://repository.apache.org";>Apache 
Nexus instance</a>. You can then continue down
+      to <a href="#Voting_On_Release">preparing the vote</a> below to prepare 
the vote.
+    </div>
+
     
 <div class="section">
-<h3><a name="Create_the_Release_Candidate"></a>Create the Release 
Candidate</h3>
+<h3><a name="Create_the_Release_Candidate_Manually"></a>Create the Release 
Candidate Manually</h3>
 
     
 <p>