aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r785079 - /websites/staging/aries/trunk/content/development/ReleaseProcessRequirements.html
Date Wed, 09 Feb 2011 14:57:17 GMT
Author: buildbot
Date: Wed Feb  9 14:57:17 2011
New Revision: 785079

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 14:57:17 2011
@@ -239,7 +239,7 @@
 <p>After release 0.3 we wanted to rexamine the release process, the primary motivation
for this was the observation that our 
 current process did not use semantic versioning, and, as an OSGi project we should be demonstrating
best OSGi practice.</p>
 
-<p>We started with the following set of requirements for any Aries release: </p>
+<p>We started with the following set of requirements for any Aries release:
 
 <table class="confluenceTable">
 <tr><th class="confluenceTh"> No. </th><th class="confluenceTh">
Description </th><th class="confluenceTh"> Met currently </th></tr>
@@ -253,18 +253,21 @@ current process did not use semantic ver
 <tr><td class="confluenceTd">  8 </td><td class="confluenceTd"> A
way to ensure that a given component doesn't have conflicting dependencies </td><td
class="confluenceTd"> ?  </td></tr>
 </table>
 
-<p>Our ideal for a release process would involve to release by module, one might visualise
the process like this: </p>
+<p>Our ideal for a release process would involve to release by module, one might visualise
the process like this:
+
+![rel](release_by_module.png)
 
-<p><img alt="rel" src="release_by_module.png" /></p>
 <p>In this case, we have a module version (independent of the version of its sub-modules)
and a set of sub-modules which may each be indepndently versioned.
 
 ## Advantages of release by module
- 1. Releasing a coherent set of bundles that have been built and run together
+
+1. Releasing a coherent set of bundles that have been built and run together
  1. Releasing a buildable set of source for all constituent bundles in one zip file
  1. A more consumable unit than a set of single bundles - easier for Aries consumers. A smaller
number of discrete downloads.
 
 ## 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 
+
+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. 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.



Mime
View raw message