From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, Neil Horman <nhorman@redhat.com>
Subject: Re: [dpdk-dev] versioning and maintenance
Date: Wed, 19 Nov 2014 11:35:08 +0000 [thread overview]
Message-ID: <20141119113507.GA2604@bricha3-MOBL3> (raw)
In-Reply-To: <5606183.AkpK27L7yz@xps13>
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.
>
Hi Thomas,
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.
/Bruce
next prev parent reply other threads:[~2014-11-19 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 11:22 Thomas Monjalon
2014-11-19 11:35 ` Bruce Richardson [this message]
2014-11-19 15:13 ` Neil Horman
2014-11-20 17:09 ` Thomas Monjalon
2014-11-20 18:25 ` Neil Horman
2014-11-20 21:08 ` Thomas Monjalon
2014-11-21 1:05 ` Neil Horman
2014-11-21 13:23 ` Thomas Monjalon
2014-11-21 20:17 ` Neil Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141119113507.GA2604@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nhorman@redhat.com \
--cc=thomas.monjalon@6wind.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).