svn commit: r1068983 - /aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext

[zo...@apache.org]

Author: zoe
Date: Wed Feb  9 17:11:17 2011
New Revision: 1068983

URL: http://svn.apache.org/viewvc?rev=1068983&view=rev
Log:
minor fix

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

Modified: aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext?rev=1068983&r1=1068982&r2=1068983&view=diff
==============================================================================
--- aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext (original)
+++ aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext Wed Feb  9 17:11:17 2011
@@ -53,8 +53,9 @@ using semantic versioning of bundles. On
 
 ### Disadvantages of the release by module process
 
- 1. 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
+ 1. 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.
  1. 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.
  1. The Maven release plugin will not cope with having different levels of snapshot in the same release.