From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: ABI/API stability in DPDK
Date: Fri, 6 Oct 2017 17:27:47 +0100
Message-ID: <bca4b60a-ace3-6b7e-f3f5-3b6529845bc6@intel.com>
References: <B27915DBBA3421428155699D51E4CFE23EDC122F@IRSMSX103.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: Kevin Traynor <ktraynor@redhat.com>, "Stokes, Ian"
 <ian.stokes@intel.com>, Luca Boccassi <luca.boccassi@gmail.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id C4A1F2C2A
 for <dev@dpdk.org>; Fri,  6 Oct 2017 18:27:49 +0200 (CEST)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23EDC122F@IRSMSX103.ger.corp.intel.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 10/6/2017 5:21 PM, Mcnamara, John wrote:
> 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.

Do we have data for this? Is it really new APIs get broken?

> 
> 
> If I missed, or misrepresented, anything please update in a reply.
> 
> John
> 
>