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

[bu...@apache.org]

Author: buildbot
Date: Thu Mar 24 09:42:12 2011
New Revision: 787452

Log:
Staging update by buildbot

Modified:
    websites/staging/aries/trunk/content/development/releasingaries.html

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 Mar 24 09:42:12 2011
@@ -246,26 +246,37 @@
 <li>Releasing a distribution - a group of bundles that work together</li>
 <li>Releasing the samples</li>
 </ol>
-<p>The outline process is the same in all three cases, further on down this page there are a lot of details about how the
-Apache release process works and how to get yourself set up to run it, you should read thos section first if this is 
+<p>The outline process is the same in all three cases, further on down this page there are details about how the
+Apache release process works and how to get set up to run it, read those sections first if this is 
 your first release. If you are already familiar with the Apache process just use the high level descriptions in the
 next few paragraphs to perform releases.</p>
 <h2 id="releasing_a_single_bundle_or_group_of_bundles">Releasing a single bundle or group of bundles.</h2>
 <h3 id="what_to_release_make_a_list">What to release? Make a list.</h3>
-<p>The Apache release process will not let you release any bundle that has dependencies in -SNAPSHOTS. If, for example,
+<p>The Apache release process will not release any bundle that has dependencies on -SNAPSHOTS. If, for example,
 a release of the blueprint API bundle is required the first step is to find and release any of
-its dependencies. Because Aries bundles are quite interdependent (see <a href="ModuleDependencies">here</a> for an idea
-of how the modules relate to each other, it may be necessary to release quite a large number of bundles.</p>
+its -SNAPSHOT dependencies. Because Aries bundles are quite interdependent (see <a href="ModuleDependencies">here</a> 
+for an idea
+of how the modules relate to each other, it may be necessary to release quite a large number of bundles. So,
+step one is to make a list. 
+<p>To help with this, there is a file called aries_release_versions.txt in the top level
+aries directory - this contains a list of all the Aries modules and their current release versions. The file
+can be recreated (if necessary)
+using the perl script list_bundles_in_aries.pl, checked into SVN under the scripts directory. The text file
+is used for later steps in the release process, so by the end of the process it will have been updated to have
+a complete list
+of all Aries modules and their most recent version numbers after the release.</p></p>
 <h3 id="how_to_deal_with_jira">How to deal with JIRA</h3>
 <p>Before actually doing any releasing work through the list of bundles and understand what defects have been fixed
 (add more about JIRA versions here)</p>
 <h3 id="what_version_will_be_released">What version will be released?</h3>
-<p>For each bundle on the list check how it's package versions have changed since the last release.
+<p>For each bundle on the list check how its package versions have changed since the last release.
 Based on this, use the versioning policy to determine the version of the bundle that should be released.</p>
 <h3 id="then_for_each_bundle">Then, for each bundle</h3>
 <ul>
-<li>mvn release prepare</li>
-<li>mvn release perform</li>
+<li>Deploy a SNAPSHOT to the maven snapshot repository (mvn deploy)</li>
+<li>Build each module and run RAT checks</li>
+<li>Create the release artifacts (mvn release prepare)</li>
+<li>Upload release artifacts to a staging repository (mvn release perform)</li>
 </ul>
 <h3 id="complete_the_process">Complete the process</h3>
 <p>Once the bundles are in the staging repository, start a vote on the release. After 72 hours close the vote. To complete