So do we have consensus for option #1 then? I think there are at least few modules we would have to update to make sure the package versions are not exported.
Jarek On Thu, May 6, 2010 at 11:42 AM, David Jencks <[email protected]> wrote: > At the moment, having thought about versions for the txmanager and jaspi > releases, I would like (1). I'm not very comfortable including versions > until there is good tool support for knowing when they change. I certainly > cannot pick a correct next package version given 2 code bases and an initial > package version. One thing I'm moderately sure of is that all the package > versions updates we've done before now are wrong :-/ > > thanks > david jencks > > On May 5, 2010, at 9:21 PM, Jarek Gawor wrote: > >> Hi, >> >> Before the milestone release we might have to figure out what osgi >> version (if any) the Geronimo packages should be exported at. I can >> think of a few possibilities: >> >> 1) No version exported for milestone releases. In the final release >> everything would be exported with "3.0.0" version. >> >> 2) Use version "3.0.0" for milestones and final release. Milestones >> are milestones and should not be used once the final is out. >> >> 3) Add some qualifier to the osgi version for milestone and final >> releases. We just need to be careful to pick the right qualifiers so >> that osgi resolves to the latest version. For example for milestones >> we could assign "3.0.0.M1" or "3.0.0.M2" but for the final we would >> have to assign "3.0.0.final" or some other qualifier that is greater >> then 'Mx' using String.compareTo() rules. >> >> Thoughts or any other possibilities? I like #3 (or some version of it) >> but I'm also ok with #2. >> >> Jarek > >
