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

[bu...@apache.org]

Author: buildbot
Date: Wed Mar 23 08:48:31 2011
New Revision: 787425

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 Wed Mar 23 08:48:31 2011
@@ -239,7 +239,39 @@
           <td height="100%" width="100%">
             <!-- Content -->
             <div class="wiki-content"><p><a name="ReleasingAries-HowtodoanAriesRelease"></a></p>
-<h1 id="how_to_do_an_aries_release_-_draft_release_by_bundle_process">How to do an Aries Release - Draft release by bundle process</h1>
+<h1 id="how_to_do_an_aries_release">How to do an Aries Release</h1>
+<p>There are three types of Aries release:</p>
+<ol>
+<li>Releasing a single Aries bundle (or group of bundles)</li>
+<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 
+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,
+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>
+<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.
+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>
+</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
+the release process it is necessary to copy the new bundles to the dist dir and update table on the web pages.</p>
+<h2 id="releasing_a_distribution">Releasing a distribution</h2>
+<h2 id="releasing_the_samples">Releasing the samples.</h2>
 <p>To create a release you will need to create the release artifacts and move
 then to various places (ultimately the Maven central repository). The Maven
 commands and general outline of the process looks like this:</p>