aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From z..@apache.org
Subject svn commit: r1068946 - /aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext
Date Wed, 09 Feb 2011 16:00:20 GMT
Author: zoe
Date: Wed Feb  9 16:00:19 2011
New Revision: 1068946

URL: http://svn.apache.org/viewvc?rev=1068946&view=rev
Log:
typo 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=1068946&r1=1068945&r2=1068946&view=diff
==============================================================================
--- aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext (original)
+++ aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext Wed Feb  9 16:00:19
2011
@@ -52,7 +52,7 @@ and it works with blueprint-core 1.1.0. 
 
 ## Releasing by bundle
 
-Other OSGi projects, for example Sling and Felix, release by module.
+Other OSGi projects, for example Sling and Felix, release by bundle.
 
 ### Advantages of releasing by bundle
  1. Other projects already do it so there is a well understood model
@@ -60,9 +60,9 @@ Other OSGi projects, for example Sling a
  1. OSGi semantic versioning can be used properly
 
 ### Disadvantages of releasing by bundle
- 1. It is more dificult for a consumer of Aries modules to understand which bundles form
a logical grouping
+ 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 seperately.
However, many bundles could be rolled up into one vote.
+   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. 



Mime
View raw message