Re: OSGi version for Geronimo packages
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 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 > >
Re: OSGi version for Geronimo packages
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
Re: OSGi version for Geronimo packages
I was actually leaning toward #2 or even #1. The benefit of #2 is that the final version is what you would normally expect and is consistent with other projects. I can certainly see the value in #3 - especially if we release multiple milestones. It makes it much easier to understand the version involved if there is a problem. But I don't like the lasting implications for our official released version. Joe On 5/6/10 12:21 AM, 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
Re: OSGi version for Geronimo packages
Right, that is why the final release needs to be called 3.0.0.final or 3.0.0.release and cannot be called 3.0.0! 3.0.0.final > 3.0.0.M1 3.0.0.release > 3.0.0.m1 Lin On Thu, May 6, 2010 at 9:42 AM, Guillaume Nodet wrote: > Keep in mind that in osgi, 3.0.0.m1 > 3.0.0 !!! > On Thu, May 6, 2010 at 15:24, Lin Sun wrote: >> >> Hi >> >> I think no. 3 is cool. some other qualifiers that I can think of are >> >> 3.0.0.m1, 3.0.0.m2, 3.0.0.release >> >> >> Lin >> >> On Thu, May 6, 2010 at 12:21 AM, 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 >> > > > > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > > Open Source SOA > http://fusesource.com > > >
Re: OSGi version for Geronimo packages
Keep in mind that in osgi, 3.0.0.m1 > 3.0.0 !!! On Thu, May 6, 2010 at 15:24, Lin Sun wrote: > Hi > > I think no. 3 is cool. some other qualifiers that I can think of are > > 3.0.0.m1, 3.0.0.m2, 3.0.0.release > > > Lin > > On Thu, May 6, 2010 at 12:21 AM, 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 > > > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
Re: OSGi version for Geronimo packages
Hi I think no. 3 is cool. some other qualifiers that I can think of are 3.0.0.m1, 3.0.0.m2, 3.0.0.release Lin On Thu, May 6, 2010 at 12:21 AM, 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 >
OSGi version for Geronimo packages
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
