aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hugh...@apache.org
Subject svn commit: r1147080 - /aries/site/trunk/content/development/releasingaries.mdtext
Date Fri, 15 Jul 2011 10:44:03 GMT
Author: hughesj
Date: Fri Jul 15 10:44:02 2011
New Revision: 1147080

URL: http://svn.apache.org/viewvc?rev=1147080&view=rev
Log:
Fix up a link

Modified:
    aries/site/trunk/content/development/releasingaries.mdtext

Modified: aries/site/trunk/content/development/releasingaries.mdtext
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/releasingaries.mdtext?rev=1147080&r1=1147079&r2=1147080&view=diff
==============================================================================
--- aries/site/trunk/content/development/releasingaries.mdtext (original)
+++ aries/site/trunk/content/development/releasingaries.mdtext Fri Jul 15 10:44:02 2011
@@ -20,7 +20,7 @@ next few paragraphs to perform releases.
 ### What to release? Make a list
 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 [here](ModuleDependencies)

+its -SNAPSHOT dependencies. Because Aries bundles are quite interdependent (see [here](moduledependencies)

 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. 



Mime
View raw message