Author: buildbot
Date: Tue Jun 4 23:28:36 2013
New Revision: 864425
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 Tue Jun 4 23:28:36 2013
@@ -1 +1 @@
-1489669
+1489671
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 Tue Jun 4
23:28:36 2013
@@ -607,6 +607,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>
</div><div class="section"><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
@@ -629,6 +630,12 @@
mvn release:prepare
</pre></div>
+ <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>
+
</div></div>
<div class="section"><h3>Create the Release Candidate<a
name="Create_the_Release_Candidate"></a></h3>
