From: Ray Kinsella <mdr@ashroe.eu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, stephen@networkplumber.org,
bruce.richardson@intel.com, ferruh.yigit@intel.com,
konstantin.ananyev@intel.com, jerinj@marvell.com,
olivier.matz@6wind.com, nhorman@tuxdriver.com,
maxime.coquelin@redhat.com, john.mcnamara@intel.com,
marko.kovacevic@intel.com, hemant.agrawal@nxp.com,
ktraynor@redhat.com, aconole@redhat.com
Subject: Re: [dpdk-dev] [PATCH v9 2/4] doc: changes to abi policy introducing major abi versions
Date: Fri, 8 Nov 2019 17:12:55 +0000 [thread overview]
Message-ID: <a3efb6e5-31e6-cf7b-8d7e-20b8b688f7f2@ashroe.eu> (raw)
In-Reply-To: <2317884.hZJoXfvIJl@xps>
On 08/11/2019 17:11, Thomas Monjalon wrote:
> 08/11/2019 13:46, Ray Kinsella:
>> This policy change introduces major ABI versions, these are
>> declared every year, typically aligned with the LTS release
>> and are supported by subsequent releases in the following year.
>> This change is intended to improve ABI stabilty for those projects
>> consuming DPDK.
>>
>> Signed-off-by: Ray Kinsella <mdr@ashroe.eu>
>> Acked-by: John Mcnamara <john.mcnamara@intel.com>
>> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
>
>> ---
>> +#. Major ABI versions are declared no more frequently than yearly. Compatibility
>> + with the major ABI version is mandatory in subsequent releases until a new
>> + major ABI version is declared.
>> +#. Major ABI version are usually but not always declared aligned with a
>> + :ref:`LTS release <stable_lts_releases>`.
>
> OK thanks
>
>> +#. The ABI version is managed at a project level in DPDK, with the ABI version
>> + reflected in all library's soname.
>
> It is not specifying the experimental lib exception.
> But I can live without it.
I will fix in a follow up on Monday.
>
>> +A new major ABI version is declared no more frequently than yearly, with
>> +declarations usually aligning with a LTS release, e.g. ABI 20 for DPDK 19.11.
>> +Compatibility with the major ABI version is then mandatory in subsequent
>> +releases until the next major ABI version is declared, e.g. ABI 21 for DPDK
>> +20.11.
>
> OK thanks
>
>> + Note that, this policy details the method by which the ABI may be changed,
>> + with due regard to preserving compatibility and observing deprecation
>> + notices. This process however should not be undertaken lightly, as a general
>> + rule ABI stability is extremely important for downstream consumers of DPDK.
>> + The API should only be changed for significant reasons, such as performance
>> + enhancements. API breakages due to changes such as reorganizing public
>> + structure fields for aesthetic or readability purposes should be avoided.
>
> OK thanks
>
>> +Libraries marked as ``experimental`` are entirely not considered part of an ABI
>> +version, and may change without warning at any time. Experimental libraries
>> +always have a major version of ``0`` to indicate they exist outside of
>> +ABI Versioning, with the minor version incremented with each ABI change
>> +to library.
>
> OK
>
>
next prev parent reply other threads:[~2019-11-08 17:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 12:46 [dpdk-dev] [PATCH v9 0/4] " Ray Kinsella
2019-11-08 12:46 ` [dpdk-dev] [PATCH v9 1/4] doc: separate versioning.rst into version and policy Ray Kinsella
2019-11-08 12:46 ` [dpdk-dev] [PATCH v9 2/4] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-08 17:11 ` Thomas Monjalon
2019-11-08 17:12 ` Ray Kinsella [this message]
2019-11-08 17:38 ` Thomas Monjalon
2019-11-11 11:03 ` Ray Kinsella
2019-11-08 12:46 ` [dpdk-dev] [PATCH v9 3/4] doc: updates to versioning guide for " Ray Kinsella
2019-11-08 12:46 ` [dpdk-dev] [PATCH v9 4/4] doc: add maintainer for abi policy Ray Kinsella
2019-11-08 17:18 ` Thomas Monjalon
2019-11-11 10:37 ` [dpdk-dev] [PATCH v10 0/3] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-11 10:37 ` [dpdk-dev] [PATCH v10 1/3] doc: separate versioning.rst into version and policy Ray Kinsella
2019-11-11 10:37 ` [dpdk-dev] [PATCH v10 2/3] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-11 10:37 ` [dpdk-dev] [PATCH v10 3/3] doc: updates to versioning guide for " Ray Kinsella
2019-11-11 11:57 ` [dpdk-dev] [PATCH v11 0/3] doc: changes to abi policy introducing major " Ray Kinsella
2019-11-11 11:57 ` [dpdk-dev] [PATCH v11 1/3] doc: separate versioning.rst into version and policy Ray Kinsella
2019-11-11 11:57 ` [dpdk-dev] [PATCH v11 2/3] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-11 11:57 ` [dpdk-dev] [PATCH v11 3/3] doc: updates to versioning guide for " Ray Kinsella
2019-11-12 7:55 ` [dpdk-dev] [PATCH v11 0/3] doc: changes to abi policy introducing major " Thomas Monjalon
2019-11-12 8:49 ` Ray Kinsella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3efb6e5-31e6-cf7b-8d7e-20b8b688f7f2@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=marko.kovacevic@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).