+1 - that's a plan. Ray K
> -----Original Message----- > From: Thomas Monjalon <tho...@monjalon.net> > Sent: Wednesday 20 November 2019 13:32 > To: Kinsella, Ray <ray.kinse...@intel.com>; Burakov, Anatoly > <anatoly.bura...@intel.com> > Cc: dev@dpdk.org; Baran, MarcinX <marcinx.ba...@intel.com>; Richardson, > Bruce <bruce.richard...@intel.com>; Mcnamara, John > <john.mcnam...@intel.com>; david.march...@redhat.com; Pawel Modrak > <pawelx.mod...@intel.com>; Yigit, Ferruh <ferruh.yi...@intel.com> > Subject: Re: [PATCH v7 01/10] config: change ABI versioning to global > > 20/11/2019 13:10, Kinsella, Ray: > > From: Burakov, Anatoly <anatoly.bura...@intel.com> > > > --- a/drivers/meson.build > > > +++ b/drivers/meson.build > > > + if is_experimental != 0 > > > + lib_version = '0.1' > > [rk] This all makes sense - except this part. > > [rk] I would expect the experimental major version to always be zero > ... > > [rk] However I would expect the minor version to increment with each > new release or at the maintainers discretion. > > Yes, the minor must be incremented with each new release if we want to > allow 2 DPDK versions to be installed in the same system. > > This policy must be changed: > " > Experimental libraries always have a major version of 0 to indicate > they exist outside of ABI Versioning, with the minor version > incremented with each ABI change to library. > " > > I propose to re-use the global ABI version for experimental by > prefixing with "0.". > So for ABI 20.0, it could be 0.20.0 or 0.200? Which one? >
