All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org, Kevin Traynor <ktraynor@redhat.com>,
	"Stokes, Ian" <ian.stokes@intel.com>,
	Luca Boccassi <luca.boccassi@gmail.com>,
	techboard@dpdk.org, aconole@redhat.com, ktraynor@redhat.com
Subject: Re: ABI/API stability in DPDK
Date: Fri, 06 Oct 2017 19:15:46 +0200	[thread overview]
Message-ID: <1688295.GhqzacEDPC@xps> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23EDC122F@IRSMSX103.ger.corp.intel.com>

06/10/2017 18:21, Mcnamara, John:
> Hi,
> 
> At the recent DPDK 2017 Userspace in Dublin we had a discussion about API/ABI stability with representation from Intel, OVS-DPDK, Debian, Red Hat and plenty of input from the floor.
> 
> The main consensus after looking at different proposals was to maintain the current process (http://dpdk.org/doc/guides/contributing/versioning.html) but to try enforce it more rigidly.
> 
> The main points to come out of this discussion were:
> 
> 1. That 3 Acks are still needed for deprecation and they should come from different companies.
> 
> 2. ABI checks to be run as part of the CI/testing so that patches that break ABI are flagged early. Note, ABI checks can be run manually as follows: http://dpdk.org/doc/guides/contributing/versioning.html#running-the-abi-validator
> 
> 3. New API's will be marked as experimental by default for 1 release minimum. This is to address the most common case for breakage which is in new APIs.

Thanks for the summary, John.

The points 1 and 3 must be approved by the technical board.

      parent reply	other threads:[~2017-10-06 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 16:21 ABI/API stability in DPDK Mcnamara, John
2017-10-06 16:27 ` Ferruh Yigit
2017-10-06 17:15 ` Thomas Monjalon [this message]

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=1688295.GhqzacEDPC@xps \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ian.stokes@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=luca.boccassi@gmail.com \
    --cc=techboard@dpdk.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.