From mboxrd@z Thu Jan 1 00:00:00 1970 From: Panu Matilainen Subject: Re: [PATCH v2] PCI: ABI change request for adding new field in rte_pci_id structure Date: Tue, 16 Feb 2016 09:55:26 +0200 Message-ID: <56C2D5EE.8070004@redhat.com> References: <1455592571-3554-1-git-send-email-ziye.yang@intel.com> <56C2D209.8000303@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: "Yang, Ziye" , "dev@dpdk.org" Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id D17F9AF85 for ; Tue, 16 Feb 2016 08:55:28 +0100 (CET) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 02/16/2016 09:43 AM, Yang, Ziye wrote: > Hi Panu, > > " ABI breakage announcements go into doc/guides/rel_notes/deprecation.rst, > see the examples there. Also you can't break the ABI in the version under development but only the next one, so right now the earliest ABI breakage opportunity is in the release *after* 16.04, which is supposed to be 16.07 according to the roadmap." > > So I only need to do the ABI breakage announcements into doc/guides/rel_notes/deprecation.rst, right? > Yes. The version-specific release notes ABI/API changes section is to be updated along with the actual changes to the code. If you haven't already done so, do read http://dpdk.org/doc/guides/contributing/versioning.html - Panu -