aries-commits mailing list archives

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

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:53:13 2011
@@ -258,17 +258,20 @@ current process did not use semantic ver
 <ol>
 <li>Conceptually very simple of consumers. For example, if as a consumer I pick up
something called Blueprint version 0.4 I know that I
 will need to get Util version 0.4 to go with it.</li>
-<li>A relatively simple release process, one JIRA component, one set of release notes.i</li>
+<li>A relatively simple release process, one JIRA component, one set of release notes.</li>
 <li>We can release a set of samples at the same version with some guarentee that the
samples all work with the release.</li>
 </ol>
 <h3 id="disadvantages_of_releasing_everything_at_once">Disadvantages of releasing everything
at once</h3>
 <ol>
-<li>Not using of OSGi semantic versioning of bundles.i After every we release we bump
the major versions of all bundles in trunk.</li>
+<li>Not using of OSGi semantic versioning of bundles. After every we release we bump
the major versions of all bundles in trunk.</li>
 </ol>
-<p>Package versions are managed separately and the Maven bundle plugin will ensure
packges are imported in the correct range based of
- the projects dependencies. Implementors need to use "provide:=true" to get the correct range.
Package export version should be maintained either using package.info or in the pom.</p>
+<p>Package versions are managed separately (correctly) and the Maven bundle plugin
will ensure packges are imported in the correct range based of
+ the projects dependencies. Implementers need to use "provide:=true" to get the correct range.
Package export version should be maintained 
+either using package.info or in the pom.xml.</p>
 <h2 id="releasing_by_module">Releasing by module</h2>
-<p><p>Our ideal for a release process would involve to release by module, one
might visualise the process like this: </p></p>
+<p><p>Our ideal for a release process would involve to release by module, this
is 
+really just an evolution of the process that we already use but it would involve 
+using semantic versioning of bundles. One might visualise the process like this: </p></p>
 <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.</p>
 



Mime
View raw message