From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: ABI/API stability in DPDK Date: Fri, 06 Oct 2017 19:15:46 +0200 Message-ID: <1688295.GhqzacEDPC@xps> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Kevin Traynor , "Stokes, Ian" , Luca Boccassi , techboard@dpdk.org, aconole@redhat.com, ktraynor@redhat.com To: "Mcnamara, John" Return-path: In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.