Author: zoe
Date: Wed Feb 9 16:53:09 2011
New Revision: 1068970
URL: http://svn.apache.org/viewvc?rev=1068970&view=rev
Log:
a bit of updated description
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=1068970&r1=1068969&r2=1068970&view=diff
==============================================================================
--- aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext
(original)
+++ aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext Wed
Feb 9 16:53:09 2011
@@ -24,19 +24,22 @@ current process did not use semantic ver
1. 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.
- 1. A relatively simple release process, one JIRA component, one set of
release notes.i
+ 1. A relatively simple release process, one JIRA component, one set of
release notes.
1. We can release a set of samples at the same version with some guarentee
that the samples all work with the release.
### Disadvantages of releasing everything at once
- 1. Not using of OSGi semantic versioning of bundles.i After every we release
we bump the major versions of all bundles in trunk.
+ 1. Not using of OSGi semantic versioning of bundles. After every we release
we bump the major versions of all bundles in trunk.
- 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.
+ 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.
## Releasing by module
-<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, 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>
