In that case I don't like the idea of released bundles using API versions < 1. What if some other bundle is providing that same package there would be no way for te resolver to know that those packages are actually not compatible.
On Fri, Dec 23, 2016 at 12:30 PM David Bosschaert < david.bosscha...@gmail.com> wrote: > Hi Bram, > > On 23 December 2016 at 11:02, Bram Pouwelse <b...@pouwelse.com> wrote: > > > > I think it would be nice if we could relax the policy at [1] a little > bit > > and say that it is ok to release bundles with provisional API in > versions < > > 1.0. The OSGi APIs always start their versions at 1.0 so an API version > 0.2 > > will never conflict with an OSGi released API. > > > > That sounds nice but you can't have major changes in the provisional API > > (or you'd loose semantic versioning). > > > > > There is a somewhat unwritten convention that API < 1.0 is 'experimental' > and therefore that exported API in versions [0.0, 1.0) does not follow > semantic versioning... Basically what you're signing up to by using this > 'provisional' API which has a version < 1.0 is that anything could > change... > > Cheers, > > David >
