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

[zo...@apache.org]

Author: zoe
Date: Wed Feb  9 16:01:47 2011
New Revision: 1068948

URL: http://svn.apache.org/viewvc?rev=1068948&view=rev
Log:
inner lists?

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=1068948&r1=1068947&r2=1068948&view=diff
==============================================================================
--- aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext (original)
+++ aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext Wed Feb  9 16:01:47 2011
@@ -62,7 +62,9 @@ Other OSGi projects, for example Sling a
 ### Disadvantages of releasing by bundle
  1. It is more difficult for a consumer of Aries modules to understand which bundles form a logical grouping
  1. There are a lot of bundles to manage independently. This has implications:
+
    1. 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.
    1. Each bundle has to have its own JIRA component
    1. 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.
- 1. There are still some issues with branching and it is still possible to get into a situation similar to that described above. 
+ 
+1. There are still some issues with branching and it is still possible to get into a situation similar to that described above.