Author: buildbot
Date: Mon Oct 29 12:18:56 2018
New Revision: 1036613

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 Mon Oct 29 12:18:56 2018
@@ -1 +1 @@
-1845109
+1845112

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 Mon Oct 29 
12:18:56 2018
@@ -459,7 +459,7 @@ mvn versions:display-plugin-updates -U</
     </div>
     
 <div class="section">
-<h3><a 
name="Configure_the_Build_to_Generate_a_Complete_Set_of_Release_Artifacts"></a>Configure
 the Build to Generate a Complete Set of Release Artifacts</h3>
+<h3><a 
name="Configure_the_Build_and_Release_Plugin_to_Generate_a_Complete_Set_of_Release_Artifacts"></a>Configure
 the Build and Release Plugin to Generate a Complete Set of Release 
Artifacts</h3>
       
 <p>
       For builds using Maven, the contents of the source and binary 
distributions are configured
@@ -487,8 +487,8 @@ mvn versions:display-plugin-updates -U</
         &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;
-        &lt;maven.compile.target&gt;1.3&lt;/maven.compile.target&gt;
+        &lt;maven.compile.source&gt;1.8&lt;/maven.compile.source&gt;
+        &lt;maven.compile.target&gt;1.8&lt;/maven.compile.target&gt;
 
         &lt;!--
           Encoding of Java source files: ensures that the compiler and
@@ -502,6 +502,13 @@ mvn versions:display-plugin-updates -U</
         
&lt;project.build.sourceEncoding&gt;${commons.encoding}&lt;/project.build.sourceEncoding&gt;
         &lt;!-- This is used by reporting plugins --&gt;
         
&lt;project.reporting.outputEncoding&gt;${commons.encoding}&lt;/project.reporting.outputEncoding&gt;
+        <!-- Commons Release Plugin -->
+        1.5
+        1.4
+        true
+        
scm:svn:https://dist.apache.org/repos/dist/dev/commons/${commons.componentid}
+        ***Release Manager Name***
+        ***Release Manager GPG Key Signature***
 
       &lt;properties&gt; </pre></div>
       
@@ -1038,6 +1045,14 @@ mvn versions:display-plugin-updates -U</
       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.
+
+      Further, the commons-release-plugin, as of 1.4, can automatically 
generate the vote email for you. When you've
+      finished staging the artifacts, run
+      
+<div>
+<pre>mvn -Prelease 
org.apache.commons:commons-release-plugin:1.4:vote-txt</pre></div>
+      This will generate a file <tt>target/vote.txt</tt> that will need to be 
altered for the vote email, but it
+      gives you a considerable head start on writing the email.
     </div>
 
     
@@ -1165,6 +1180,14 @@ mvn versions:display-plugin-updates -U</
   
 <div class="section">
 <h2><a name="Voting_On_Release"></a>Voting On Release</h2>
+
+    
+<div class="section">
+<h3><a name="Using_commons-release-plugin"></a>Using 
commons-release-plugin</h3>
+      The vote email should have been mostly generated for you by the plugin. 
See the section above pertaining
+      to the commons-release-plugin for more details.
+    </div>
+
     
 <div class="section">
 <h3><a name="aVOTE_Release_Foo_1.2_based_on_RC1"></a>[VOTE] Release Foo 1.2 
based on RC1</h3>


Reply via email to