Author: mbenson
Date: Tue Jan 7 16:42:40 2014
New Revision: 1556268
URL: http://svn.apache.org/r1556268
Log:
CMS commit to commons by mbenson
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=1556268&r1=1556267&r2=1556268&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/releases/prepare.xml (original)
+++ commons/cms-site/trunk/content/xdoc/releases/prepare.xml Tue Jan 7
16:42:40 2014
@@ -20,7 +20,7 @@
<properties>
<title>Preparations for a Release</title>
- <author email="[email protected]">Commons Documentation Team</author>
+ <author email="[email protected]">Apache Commons Documentation
Team</author>
</properties>
<body>
@@ -29,11 +29,11 @@
This document contains a mixture of information, advice and examples.
It is intended to be a recommendation of best practices for Commons
components.
The instructions provided here are consistent with, but not a
replacement for
- the <a href="http://www.apache.org/dev/release.html";>ASF Release
Guidlines.</a>
+ the <a href="http://www.apache.org/dev/release.html";>ASF Release
Guidelines.</a>
</p>
- <p>Commons uses the Nexus installation at the Apache Software Foundation
to stage Maven artifacts
- before the release and later publish them, the Commons Parent POM contains
all the necessary configuration.
- This guide covers deploying to Nexus using Maven, for alternatives see
+ <p>The Apache Commons project uses the Nexus installation at the Apache
Software Foundation to stage Maven artifacts
+ before the release and later publish them; the Commons Parent POM contains
all the necessary configuration.
+ This guide covers deploying to Nexus using Maven. For alternatives see
<a href="http://www.apache.org/dev/publishing-maven-artifacts.html";>the
ASF wide documentation</a>.
If this is the first time you are publishing to the ASF's Nexus instance
you'll need to <a
href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env";>prepare
@@ -92,9 +92,9 @@
<subsection name='Consider a Release Branch'>
<p>
Consider whether a release branch is needed before preparing for the new
release. In general,
- commons components are small enough that there is no need for a release
branch, but if
- active development wants to continue on the next version while a release
is being made then
- trunk should be branched to allow development to continue.
+ Commons components are small enough that there is no need for a release
branch, but if
+ active development will continue on the next version while a release is
being made then
+ trunk should be branched to allow this.
If a release branch is taken then work will be required to merge any
changes back
into the trunk.
</p>
@@ -115,7 +115,7 @@
</p>
<p>Alternatively, use "svn cp URLsrc URLtag"</p>
<pre>
- svn cp -m "Creating foo-1.2-release branch" \
+ svn cp -m "Creating foo-1.2-release branch" \
https://svn.apache.org/repos/asf/commons/proper/foo/trunk \
https://svn.apache.org/repos/asf/commons/proper/foo/branches/foo-1.2-release
</pre>
