svn commit: r823599 - in /websites/staging/aries/trunk/content: ./ development/releasingaries.html

[bu...@apache.org]

Author: buildbot
Date: Thu Jun 28 11:26:57 2012
New Revision: 823599

Log:
Staging update by buildbot for aries

Modified:
    websites/staging/aries/trunk/content/   (props changed)
    websites/staging/aries/trunk/content/development/releasingaries.html

Propchange: websites/staging/aries/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 28 11:26:57 2012
@@ -1 +1 @@
-1354938
+1354941

Modified: websites/staging/aries/trunk/content/development/releasingaries.html
==============================================================================
--- websites/staging/aries/trunk/content/development/releasingaries.html (original)
+++ websites/staging/aries/trunk/content/development/releasingaries.html Thu Jun 28 11:26:57 2012
@@ -509,7 +509,7 @@ trunk.</p>
 <li>What is the new development version for "Aries :: Top Parent POM"? (org.apache.aries:parent) 0.6-SNAPSHOT: : 0.5.1</li>
 </ol>
 <p>i.e. take the defaults for the last two questions, but change the release version if required. The last person doing a release didn't know whether the next version released from the trunk would have a major, minor or micro version number change - they couldn't know until those changes were made! - but they had to make a guess. Now is the time 
-to correct their guess. Similarly, you won't know what the next release number should be, but you need to use /something/, so accept the default. </p>
+to correct their guess. Similarly, you won't know what the next release number should be, but you need to use <em>something</em>, so accept the default. </p>
 </li>
 <li>
 <p>Note 3: Since the release plugin makes changes in SCM, use a JIRA for the release (ARIES-XXX here) in the commit comment to make it easier to see what's changed.</p>