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

[bu...@apache.org]

Author: buildbot
Date: Thu Jun 28 11:25:14 2012
New Revision: 823597

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:25:14 2012
@@ -1 +1 @@
-1354925
+1354938

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:25:14 2012
@@ -508,12 +508,15 @@ trunk.</p>
 <li>What is SCM release tag or label for "Aries :: Top Parent POM"? (org.apache.aries:parent) parent-0.5: :</li>
 <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. You don't know whether the next version released from the trunk will have a major, minor or micro version number change - you won't know until those changes are made! - but you have to make a guess. The person doing the next release can make the decision and move to <em>module</em>-<em>new version</em>-SNAPSHOT.
-  * 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
-<em> Note 3: mvn release:clean will do </em>most* of the cleaning up in the event of failures.
-  * Note 4: If on mvn release:prepare you get an error from SVN similar to https://svn.apache.org/repos/asf/!svn/bc/1182408/aries/tags/parent-0.5/default-parent/java5-parent/org.apache.aries.bundle.i.am.releasing does not exist then it's because there's no scm element in the pom.xml for the module you're releasing.</p>
+<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>
 </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>
+</li>
+<li>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.</li>
+<li>Note 5: mvn release:clean will do <em>most</em> of the cleaning up in the event of failures.</li>
+<li>Note 6: If on mvn release:prepare you get an error from SVN similar to https://svn.apache.org/repos/asf/!svn/bc/1182408/aries/tags/parent-0.5/default-parent/java5-parent/org.apache.aries.bundle.i.am.releasing does not exist then it's because there's no scm element in the pom.xml for the module you're releasing.</li>
 </ul>
 <p>This will put release artifacts into an Apache <a href="https://repository.apache.org/index.html#view-repositories;staging.html">staging repository </a>. You will need to log in to see it.
 If nothing appears in a staging repo you should stop here and work out why.