svn commit: r1354939 - /aries/site/trunk/content/development/releasingaries.mdtext

[cu...@apache.org]

Author: cumminsh
Date: Thu Jun 28 11:26:17 2012
New Revision: 1354939

URL: http://svn.apache.org/viewvc?rev=1354939&view=rev
Log:
Improving formatting.

Modified:
    aries/site/trunk/content/development/releasingaries.mdtext

Modified: aries/site/trunk/content/development/releasingaries.mdtext
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/releasingaries.mdtext?rev=1354939&r1=1354938&r2=1354939&view=diff
==============================================================================
--- aries/site/trunk/content/development/releasingaries.mdtext (original)
+++ aries/site/trunk/content/development/releasingaries.mdtext Thu Jun 28 11:26:17 2012
@@ -295,7 +295,7 @@ For each bundle that needs to be release
     1. What is the new development version for "Aries :: Top Parent POM"? (org.apache.aries:parent) 0.6-SNAPSHOT: : 0.5.1
 
     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. 
+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. 
 
   * 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.
   * Note 4: The task will appear to hang at the end. It's waiting ten seconds to do the tagging, to ensure everything works in Europe, where svn is mirrored from a US master.