svn commit: r785090 - /websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html

[buildbot]

Author: buildbot
Date: Wed Feb  9 16:06:06 2011
New Revision: 785090

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 16:06:06 2011
@@ -295,7 +295,7 @@ and it works with blueprint-core 1.1.0. 
 <ol>
 <li>It is more difficult for a consumer of Aries modules to understand which 
bundles form a logical grouping</li>
 <li>There are a lot of bundles to manage independently. This has 
implications:<br/><ul>
-<li>Releasing - mvn release:prepare an so on,  needs to be run for each bundle 
separately. However, many bundles could be rolled up into one vote.</li>
+<li>Releasing - mvn release:prepare, and so on,  needs to be run for each 
bundle separately. However, many bundles could be rolled up into one vote.</li>
 <li>Each bundle has to have its own JIRA component</li>
 <li>Our svn tree would need to be restructured - probably in a similar way to 
the Sling tree. Each bundle would have its own trunk &amp; branches.</li>
 </ul>