From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id B9DC71B1EC for ; Fri, 6 Oct 2017 18:21:52 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Oct 2017 09:21:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,484,1500966000"; d="scan'208,217";a="143606983" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by orsmga002.jf.intel.com with ESMTP; 06 Oct 2017 09:21:50 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.49]) by IRSMSX108.ger.corp.intel.com ([169.254.11.167]) with mapi id 14.03.0319.002; Fri, 6 Oct 2017 17:21:49 +0100 From: "Mcnamara, John" To: "dev@dpdk.org" CC: Kevin Traynor , "Stokes, Ian" , Luca Boccassi Thread-Topic: ABI/API stability in DPDK Thread-Index: AdM+vRkNZ86iF8/rR0iGZxdgD1AX2Q== Date: Fri, 6 Oct 2017 16:21:48 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMjIyNTMzNTctNTQyMC00NzVkLTlhYmMtOGNhMTY5NTMxZWQ1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IllxT0FNOE82SEhxQ21pQ3NJVW9weTlFRjZIOFV2bkNaWGpGUEVrOGhmeXc9In0= dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.180] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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:21:53 -0000 Hi, At the recent DPDK 2017 Userspace in Dublin we had a discussion about API/A= BI 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 d= ifferent companies. 2. ABI checks to be run as part of the CI/testing so that patches that brea= k ABI are flagged early. Note, ABI checks can be run manually as follows: h= ttp://dpdk.org/doc/guides/contributing/versioning.html#running-the-abi-vali= dator 3. New API's will be marked as experimental by default for 1 release minimu= m. This is to address the most common case for breakage which is in new API= s. If I missed, or misrepresented, anything please update in a reply. John