Semantic Versioning mandates not only package version changes but also bundle version changes. Compare with https://www.osgi.org/developer/white-papers/semantic-versioning/bundles-and-fragments/ <https://www.osgi.org/developer/white-papers/semantic-versioning/bundles-and-fragments/>
" The version of a bundle must therefore semantically aggregate the semantics of all its constituent packages. If any of these packages are incompatible with its providers then the bundle version must increment the minor version. If any of these packages are incompatible with consumers, the bundle version must increment the major version." This is sometimes conflicting with odd/even versions: https://github.com/bndtools/bnd/issues/3446 <https://github.com/bndtools/bnd/issues/3446> Konrad > On 30. Sep 2019, at 12:09, Marcel Reutegger <[email protected]> > wrote: > > Hi, > > In my view, using an odd numbered snapshot version would be better > as well. According to versionatorr, OSGi will consider 1.20-SNAPSHOT > more recent than 1.20.0. > > http://versionatorr.appspot.com/?a=1.20-SNAPSHOT&b=1.20.0 > > Regards > Marcel > > On 27.09.19, 11:57, "Julian Reschke" <[email protected]> wrote: > > On 04.03.2019 14:29, Davide Giannella wrote: >> ... > > Picking up an old thread... > > So we've released 1.12.0, 1.14.0, 1.16.0, and will release 1.18.0 next > week. > > What we apparently did not discuss what the project version for trunk > should be in the meantime. > > So far, we've been using 1.12-SNAPSHOT, etc, and we are on 1.20-SNAPHOT > right now. > > This however seems incorrect to me; shouldn't it be 1.19-SNAPSHOT? > > For this release I'd like to avoid any changes, but for future releases > I'd like to document that we're using an odd-numbered version. > > Feedback appreciated, > > Julian > > >
