Author: buildbot
Date: Sun Mar 17 06:51:34 2013
New Revision: 854819
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 Sun Mar 17 06:51:34 2013
@@ -1 +1 @@
-1457386
+1457387
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 Sun Mar 17
06:51:34 2013
@@ -582,7 +582,7 @@
<p>
Now create the tag for the release candidate. There are two options
how to do that,
you can either use the Maven release plugin or create the tag
manually.</p>
-
+ <a name="Manual_Method"><div class="section"><h4>Manual Method<a
name="Manual_Method"></a></h4></a>
<p>Create a clean SVN workspace for the release candidate:</p>
<div><pre>
svn co https://svn.apache.org/repos/asf/commons/proper/foo/trunk
foo-m.n.o-RC1
@@ -604,9 +604,8 @@
<div><pre>
svn copy foo-m.n.o-RC1 -m "Creating foo-m.n.o-RC1 tag"
https://svn.apache.org/repos/asf/commons/proper/foo/tags/foo-m.n.o-RC1
</pre></div>
-
-
+ <a name="Maven_Release_Plugin"></div><div class="section"><h4>Maven
Release Plugin<a name="Maven_Release_Plugin"></a></h4></a>
<p>When using the release plugin, please verify that your poms will
not lose content when they are rewritten during the
release process.</p>
@@ -626,9 +625,8 @@
<div><pre>
mvn release:prepare
</pre></div>
-
- </div>
+ </div></div>
<div class="section"><h3>Create the Release Candidate<a
name="Create_the_Release_Candidate"></a></h3>
<p>
