From: Ray Kinsella <mdr@ashroe.eu>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org, thomas@monjalon.net, stephen@networkplumber.org,
bruce.richardson@intel.com, ferruh.yigit@intel.com,
konstantin.ananyev@intel.com, jerinj@marvell.com,
olivier.matz@6wind.com, maxime.coquelin@redhat.com,
john.mcnamara@intel.com, marko.kovacevic@intel.com,
hemant.agrawal@nxp.com, ktraynor@redhat.com
Subject: Re: [dpdk-dev] [PATCH v4 1/4] doc: separate versioning.rst into version and policy
Date: Fri, 27 Sep 2019 16:22:25 +0100 [thread overview]
Message-ID: <0f4c6363-cda6-54be-5fc8-38b8f627e745@ashroe.eu> (raw)
In-Reply-To: <20190925122417.GB31002@hmswarspite.think-freely.org>
On 25/09/2019 13:24, Neil Horman wrote:
> On Wed, Sep 25, 2019 at 11:23:53AM +0100, Ray Kinsella wrote:
> This seems..confusing. In patch 0:
> =================================================================
> * DPDK v20 is declared as the supported ABI version for one year, aligned with
> the DPDK v19.11 (LTS) release. All library sonames are updated to reflect the
> new ABI version, e.g. librte_eal.so.20, librte_acl.so.20...
> * DPDK v20.02 .. v20.08 releases are ABI compatible with the DPDK v20 ABI. ABI
> changes are permitted from DPDK v20.02 onwards, with the condition that ABI
> compatibility with DPDK v20 is preserved.
> * DPDK v21 is declared as the new supported ABI version for two years, aligned
> with the DPDK v20.11 (LTS) release. The DPDK v20 ABI is now depreciated,
> library sonames are updated to v21 and ABI compatibility breaking changes may
> be introduced.
> ===================================================================
Actually Neil,
Apologies now I am taking a closer look at your email.
I understand what is going on.
Patch 1/4 separates the ABI Policy from the detail of ABI Version
management, but it is still old policy that your where reading at this
point, hence all the references to DPDK 2.0 and why it doesn't
Patch 2/4 is the _new policy_, where you will see that all references to
2.0 have been removed.
You other points around the needing a taxonomy still are 100% valid
though and I am working on adding a diagram.
Ray K
next prev parent reply other threads:[~2019-09-27 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 10:23 [dpdk-dev] [PATCH v4 0/4] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-09-25 10:23 ` [dpdk-dev] [PATCH v4 1/4] doc: separate versioning.rst into version and policy Ray Kinsella
2019-09-25 12:24 ` Neil Horman
2019-09-25 13:01 ` Ray Kinsella
2019-09-25 14:34 ` Neil Horman
2019-09-27 15:22 ` Ray Kinsella [this message]
2019-09-27 15:43 ` Aaron Conole
2019-09-27 16:43 ` Ray Kinsella
2019-09-25 10:23 ` [dpdk-dev] [PATCH v4 2/4] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-09-25 10:23 ` [dpdk-dev] [PATCH v4 3/4] doc: updates to versioning guide for " Ray Kinsella
2019-09-25 10:23 ` [dpdk-dev] [PATCH v4 4/4] doc: add maintainer for abi policy 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=0f4c6363-cda6-54be-5fc8-38b8f627e745@ashroe.eu \
--to=mdr@ashroe.eu \
--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).