aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r785099 - /websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html
Date Wed, 09 Feb 2011 17:11:21 GMT
Author: buildbot
Date: Wed Feb  9 17:11:21 2011
New Revision: 785099

Log:
Staging update by buildbot

Modified:
    websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html

Modified: websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html
==============================================================================
--- websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html (original)
+++ websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html Wed Feb
 9 17:11:21 2011
@@ -283,8 +283,9 @@ using semantic versioning of bundles. On
 </ol>
 <h3 id="disadvantages_of_the_release_by_module_process">Disadvantages of the release
by module process</h3>
 <ol>
-<li>We would want to release a whole module at once, this would mean re-releasing bundles
at the same level 
- (and with the same content) as a previous release. This is not a major issue</li>
+<li>We would have to release a whole module at once, this would mean re-releasing bundles
at the same level 
+ (and with the same content) as a previous release. This is not a major issue but we would
probably not want them in the 
+www.apache.org/dist/aries directory.</li>
 <li>Developer would need to be careful to version submodules poms independently from
the parent/reactor pom. Again, 
  not a major issue but a change from the way we work at the moment.</li>
 <li>The Maven release plugin will not cope with having different levels of snapshot
in the same release. 



Mime
View raw message