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

[bu...@apache.org]

Author: buildbot
Date: Thu Mar 24 15:07:46 2011
New Revision: 787462

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 15:07:46 2011
@@ -283,11 +283,15 @@ Based on this, use the <a href="versionp
 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>
 <p>A distribution is just a collection of Aries bundles which have already been released.
-The distribution is just a convenient way for consumers to download related bundles.
+The distribution is just a convenient way for consumers to download aries bundles and all
+of the Aries bundles that they depend on.
 There are three distributions:
   * Blueprint
   * Application (isolating framework)
   * Application (non-isolating framework)</p>
+<p>The release process is just the same as for everything else, again, the right time to release these is
+immediately after a bundle(s) release when you have a collection of artifacts that 
+work together.</p>
 <h2 id="releasing_the_samples">Releasing the samples</h2>
 <p>The Aries samples are designed to work across all the Aries modules. Samples are released as a single
 module. All of the Aries dependencies are listed in the top level samples pom. In