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
