Author: buildbot
Date: Wed Feb 9 16:03:37 2011
New Revision: 785088
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:03:37 2011
@@ -294,19 +294,13 @@ and it works with blueprint-core 1.1.0.
<h3 id="disadvantages_of_releasing_by_bundle">Disadvantages of releasing by
bundle</h3>
<ol>
<li>It is more difficult for a consumer of Aries modules to understand which
bundles form a logical grouping</li>
-<li>
-<p>There are a lot of bundles to manage independently. This has
implications:</p>
-</li>
-<li>
-<p>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.</p>
-</li>
+<li>There are a lot of bundles to manage independently. This has
implications:<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>Each bundle has to have its own JIRA component</li>
-<li>
-<p>Our svn tree would need to be restructured - probably in a similar way to
the Sling tree. Each bundle would have its own trunk & branches.</p>
-</li>
-<li>
-<p>There are still some issues with branching and it is still possible to get
into a situation similar to that described above. </p>
+<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 & branches.</li>
+</ul>
</li>
+<li>There are still some issues with branching and it is still possible to get
into a situation similar to that described above. </li>
</ol></div>
<!-- Content -->
</td>
