[dpdk-dev] versioning and maintenance
bruce.richardson at intel.com
Wed Nov 19 12:35:08 CET 2014
On Wed, Nov 19, 2014 at 12:22:14PM +0100, Thomas Monjalon wrote:
> Following the discussion we had with Neil during the conference call,
> I suggest this plan, starting with the next release (2.0):
> - add version numbers to libraries
> - add version numbers to functions inside .map files
> - create a git tree dedicated to maintenance and API compatibility
> It means these version numbers must be incremented when breaking the API.
> Though the old code paths will be maintained and tested separately by volunteers.
> A mailing list for maintenance purpose could be created if needed.
I really think that the versionning is best handled inside the main repository
itself. Given that the proposed deprecation policy is over two releases i.e. an
API is marked deprecated in release X and then removed in X+1, I don't see the
maintaining of old code paths to be particularly onerous.
More information about the dev