From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id C4A1F2C2A for ; Fri, 6 Oct 2017 18:27:49 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Oct 2017 09:27:48 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,484,1500966000"; d="scan'208";a="907480727" Received: from unknown (HELO [10.241.225.2]) ([10.241.225.2]) by FMSMGA003.fm.intel.com with ESMTP; 06 Oct 2017 09:27:47 -0700 To: "Mcnamara, John" , "dev@dpdk.org" Cc: Kevin Traynor , "Stokes, Ian" , Luca Boccassi References: From: Ferruh Yigit Message-ID: Date: Fri, 6 Oct 2017 17:27:47 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] ABI/API stability in DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 16:27:50 -0000 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 > >