svn commit: r787474 - in /websites/production/aries: ./ content/development/releasingaries.html

[zo...@apache.org]

Author: zoe
Date: Thu Mar 24 16:35:24 2011
New Revision: 787474

Log:
Publishing merge to aries site by zoe

Modified:
    websites/production/aries/   (props changed)
    websites/production/aries/content/development/releasingaries.html

Propchange: websites/production/aries/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Thu Mar 24 16:35:24 2011
@@ -1 +1 @@
-/websites/staging/aries/trunk:782169-787470
+/websites/staging/aries/trunk:782169-787473

Modified: websites/production/aries/content/development/releasingaries.html
==============================================================================
--- websites/production/aries/content/development/releasingaries.html (original)
+++ websites/production/aries/content/development/releasingaries.html Thu Mar 24 16:35:24 2011
@@ -251,7 +251,7 @@ Apache release process works and how to 
 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>
+<h3 id="what_to_release_make_a_list">What to release? Make a list!</h3>
 <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 -SNAPSHOT dependencies. Because Aries bundles are quite interdependent (see <a href="ModuleDependencies">here</a>