Versions (leading on from releases discussions)

[zoe slattery]

Hi - I had a very useful IRC discussion with Guillaume trying to make 
sure that we had a common understanding of the versioning policy that is 
used in Aries today and the implications of changing it to use OSGi 
semantic versioning for packages, and maybe for bundles.

I believe we agreed that we do not use package versioning correctly at 
the moment and, in order to do so, we would have to break the way that 
that package versions are derived from bundle versions and manage 
package versions independently (manually).

We didn't agree on the right thing to do with bundle versions (we didn't 
disagree either, I just don't know what the right answer is) , in 
particular where a module has a set of sub-modules (bundles). The 
options are either:

1) To agree not to follow  bundle versioning policy. So all teh 
submodules in a module would have teh same bundle version irrespective 
of whether they have changed.
2) To follow it and try and cope with what could become an unholy mess 
of bundle versions in the development code base.

I tried to draw this out in a set of charts, here: 
https://svn.apache.org/repos/asf/aries/slides/aries-version.odp, and 
I've just realised that not everyone will have odp so I'll put a pdf in 
there too.

These are for discussion and illustration of the problem - feed back 
welcome.


Zoe