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

[hu...@apache.org]

Author: hughesj
Date: Fri Jul 15 10:44:51 2011
New Revision: 792735

Log:
Publishing merge to aries site by hughesj

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

Propchange: websites/production/aries/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Fri Jul 15 10:44:51 2011
@@ -1 +1 @@
-/websites/staging/aries/trunk:782169-792698
+/websites/staging/aries/trunk:782169-792734

Modified: websites/production/aries/content/development/releasingaries.html
==============================================================================
--- websites/production/aries/content/development/releasingaries.html (original)
+++ websites/production/aries/content/development/releasingaries.html Fri Jul 15 10:44:51 2011
@@ -263,7 +263,7 @@ next few paragraphs to perform releases.
 <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> 
+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.