You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by se...@apache.org on 2013/06/05 01:22:25 UTC

svn commit: r1489671 - /commons/cms-site/trunk/content/xdoc/releases/prepare.xml

Author: sebb
Date: Tue Jun  4 23:21:32 2013
New Revision: 1489671

URL: http://svn.apache.org/r1489671
Log:
More explanations

Modified:
    commons/cms-site/trunk/content/xdoc/releases/prepare.xml

Modified: commons/cms-site/trunk/content/xdoc/releases/prepare.xml
URL: http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/releases/prepare.xml?rev=1489671&r1=1489670&r2=1489671&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/releases/prepare.xml (original)
+++ commons/cms-site/trunk/content/xdoc/releases/prepare.xml Tue Jun  4 23:21:32 2013
@@ -465,6 +465,7 @@
       <p>
         Do NOT check the updated workspace back into the development trunk.
         It's important to only have SNAPSHOT versions in trunk; only tags should have non-SNAPSHOT versions.
+        Also, by leaving trunk unchanged, nothing needs to be reverted if the RC vote fails and the Rc needs to be re-rolled.
       </p>
       <h4>Maven Release Plugin<a name="Maven_Release_Plugin"></a></h4>
         <p>When using the release plugin, please verify that your poms will not lose content when they are rewritten during the
@@ -487,6 +488,12 @@
       mvn release:prepare
       </pre>
 
+      <p>
+        The Maven release:prepare goal updates the trunk tag to the next SNAPSHOT release. 
+        If the RC vote fails, this will need to be reverted before re-rolling the RC.
+        (the manual method described above avoids this problem)
+      </p>
+      
     </subsection>
     <subsection name="Create the Release Candidate">