From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 147072B9A; Fri, 6 Oct 2017 19:15:49 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9D26C20C8C; Fri, 6 Oct 2017 13:15:47 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 06 Oct 2017 13:15:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=wx+ZLAZCoBaiv1/ 25fy1qBhdtIBP7AcCBb5JHsVdWLY=; b=AArYKqY22PhZC+0tQ+NqrrIo49GSu0b fP23E06MGcoz8jy5pH4fpb//RoxGi3917ABo2CuLOtOMsGkVk829EzAWa+iWSAR2 9uOKFQhugrb01Wykol/DPL0tQseD27D7jRrKI6QJbCoy5zrEowJQozGD3oJH9r2J vhEZqSGT9OzM= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=wx+ZLAZCoBaiv1/25fy1qBhdtIBP7AcCBb5JHsVdWLY=; b=XlAZOMEB 1Od+kX/EjMXPSH3qXubaNdlqI6uX+XcSHfjECTdf0fgPEo60yrjyG+E0ZLnhdQHK +yBW/szDZ3reQIFzrdYDxKR7kDUX2j17AUu1Rgn/EpfnSAsjiFKe3xKM0HBZcFXW aSX9IR+M4iuemFpCJ9bC5xXERRlQPPTcQhd6uo4ikT5HTq9WsdtL4WBJk7rFU1rB 6MQ2k3GA1uiR3WK3JSPUFbfy3uJf4tUldxjwlWMgstlHvovvib0LxIjSGr+KB01d lcyY12Veb5zXmF0Yflc3WEwrzkqFAxKKdw5lJ5W5FRD4uBkttimei8XUPnzIAGOL S+kF2KpJgzmuOQ== X-ME-Sender: X-Sasl-enc: YbyNjzh63oC/QUtuB1fHCP3bYheHU4wz5t4MXdFE4JOM 1507310147 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4CB8E2486C; Fri, 6 Oct 2017 13:15:47 -0400 (EDT) From: Thomas Monjalon To: "Mcnamara, John" Cc: dev@dpdk.org, Kevin Traynor , "Stokes, Ian" , Luca Boccassi , techboard@dpdk.org, aconole@redhat.com, ktraynor@redhat.com Date: Fri, 06 Oct 2017 19:15:46 +0200 Message-ID: <1688295.GhqzacEDPC@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 17:15:49 -0000 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.