>> Sometimes no exported package changes but you still have new >> functionality. So a increasing the minor version instead of the bugfix >> version makes sense.
I agree, but this has always been the case. The version reflects the semantics of the package or bundle, not the API. So if new function is added and no externals (interfaces etc) change, then the minor version must still get bumped. This is so that a client of that package can indicate its requirement for the new function. Also, version numbers don't get bumped unnecessarily. Say a bundle has changes that would ordinarily mean a minor version change, then the minor version is bumped and the micro version zero'd out. All the other bundles being co-released (assuming they don't have significant ie major version changes) will also have their minor version bumped (and micro version reset). I would object to a the minor version (say) being bumped when all that has changed across the whole release is micro changes. On 19 August 2015 at 13:04, John W Ross <jwr...@us.ibm.com> wrote: > Christian made a caveat in a previous message [1]. Given that, a bundle > version update will simply mean that the bundle is part of the X.X.X > release of the Z project and that something in the project changed. > > [1] >>> For the bundle version I think the version policy described makes sense >>> in general but I would not mind if the version jump is bigger than the >>> jump described in the policy. >>> Sometimes no exported package changes but you still have new >>> functionality. So a increasing the minor version instead of the bugfix >>> version makes sense. > >> From: Daniel Kulp <dk...@apache.org> >> To: dev@aries.apache.org >> Date: 08/18/2015 06:12 PM >> Subject: Re: Versioning Policy >> >> >> > On Aug 18, 2015, at 12:35 PM, John W Ross <jwr...@us.ibm.com> wrote: >> > Previously, you could count on a minor bundle version increment to >> > correspond to at least one package in that bundle also having a minor >> > version increment. I guess what it would tell me now is that at least > one >> > of the packages in one of the bundles within the same project received > a >> > minor version increment, although not necessarily this particular > bundle? >> >> Correct. >> >> Dan >> >> >> >> > >> >> From: Christian Schneider <ch...@die-schneider.net> >> >> To: dev@aries.apache.org >> >> Date: 08/18/2015 11:10 AM >> >> Subject: Re: Fw: Versioning Policy >> >> Sent by: Christian Schneider <cschneider...@gmail.com> >> >> >> >> As long as the bundle exports the packages with the same version as >> >> before it should not have any influence. >> >> The only major problem would be if people use require bundle instead > of >> >> import package. >> >> >> >> Christian >> >> >> >> >> >> >> >> On 18.08.2015 17:56, John W Ross wrote: >> >>> There are no concerns with a bundle version changing even though the >> >>> content of the bundle did not change? >> >>> >> >>> >> >> >> >> >> >> -- >> >> Christian Schneider >> >> http://www.liquid-reality.de >> >> >> >> Open Source Architect >> >> http://www.talend.com >> >> >> > >> >> -- >> Daniel Kulp >> dk...@apache.org - http://dankulp.com/blog >> Talend Community Coder - http://coders.talend.com >> >
