+1 .... although I do share Guillaume's concerns.
Z
+/-0
While I think the goals are good (i.e. mainly correct semantic
versionning), I think the additional amount of work for JIRA (tracking
each bundle individually with each version) and for the Release
Manager (which has a lot to decide and verify) is worrying. I hope
I'll be proven wrong and that next releases will go smoothly.
Thx Zoe for leading the discusion.
On Wed, Mar 2, 2011 at 15:59, zoe slattery<[email protected]> wrote:
Hi all
We have had a huge amount of discussion on the mailing list about the merits
(and otherwise) of moving to a release-by-bundle scheme. I'd like to draw
that to a close with a vote.
To summarise, we currently have a release by module scheme but cannot use
OSGi semantic versioning within this scheme because the maven release plugin
will not handle releasing sub-modules with different versions. The other
solution that has been considered is de-coupling the 'artifact-version' from
the bundle's version, a number of people felt that this would be confusing.
The proposal is to move to release by bundle and distribution, this will
give us the ability to
* have correct OSGi bundle versioning
* use the apache maven release process without changing it
* not re-release the same code over again
* supply our users with groups of bundles that work together
This will involve more work for the release manager, but that is the only
major drawback.
The vote:
[+1] Move our process to release by bundle
[0] Don't care either way
[-1] Stay with the process as it is
The vote will run for 72 hours.
Zoė
