From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7793CA3201 for ; Mon, 21 Oct 2019 11:50:53 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5359A1BE85; Mon, 21 Oct 2019 11:50:53 +0200 (CEST) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by dpdk.org (Postfix) with ESMTP id 4872B1B94A for ; Mon, 21 Oct 2019 11:50:51 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id C03B4B01B; Mon, 21 Oct 2019 05:50:48 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 21 Oct 2019 05:50:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=qfEREqBaltiKnPdLF3fcckQgJfyjd5lo6zgS8q4vOWg=; b=CIs31/YMeVaz qGM0qGBd3NKR0dWhcqd1wKJokz3zNXN5EKGYWG/05+5tdQzBYRmCIgAnJopmc94u JsBe8BmtMAU8Nn/a3zm3sH67Ra/gNU8Z/Im+FH3hHqnKX2pxxOIekFaTEjd6CMHN hG6Ym1F0j4wxUJ3QQuEsTIDOGi7I958= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=qfEREqBaltiKnPdLF3fcckQgJfyjd5lo6zgS8q4vO Wg=; b=bO/kPmJDzYyCkUliOS/p+L9Ra2vRQWHSG9nYGUVFYbhZM2mTCNL7IfyT+ wOM/a+q1ipQfKsaKDFhgtGRyglXu6c4d67qH6Sbg398H8OOVcqIvB3WKHacQbPlp jwM+9D+W91nM0HAFml81S1IkQuxmJqbP1PaaR3dPJyYlurZYpqRs/jy1vdzbxijk LP+9DDod2pTtlI05SDI/x0Gtwv/+rn8vn0oFsFXma0oiFM549yn+HSYZGWOyIh7U 2cPQdY6WaKVrYsLv963T0/gATxVcA/ilWXqISLeKKFVpS60y66Ui7YyLeJq4dhlg EJ+KXH7uaGa2cl7f7NvjgnB6FJwcQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrkeehgddvudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhgggfgtsehtufertd dttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehm ohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfedrudekgeenucfrrg hrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthenucev lhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id D4B0FD6005F; Mon, 21 Oct 2019 05:50:44 -0400 (EDT) From: Thomas Monjalon To: Ray Kinsella 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 Date: Mon, 21 Oct 2019 11:50:42 +0200 Message-ID: <4306711.lZEasSuxhK@xps> In-Reply-To: <1569603283-1857-1-git-send-email-mdr@ashroe.eu> References: <1569603283-1857-1-git-send-email-mdr@ashroe.eu> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v6 0/4] doc: changes to abi policy introducing major abi versions 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 27/09/2019 18:54, Ray Kinsella: > TL;DR abbreviation: > A major ABI version that all DPDK releases during a one year period > support. ABI versioning is managed at a project-level, in place of library-level > management. ABI changes to add new features are permitted, as long as ABI > compatibility with the major ABI version is maintained. > > Detail: > This patch introduces major ABI versions, supported for one year and released > aligned with the LTS release. This ABI version is then supported by all > subsequent releases within that one year period. The intention is that the one > year support period, will then be reviewed after the initial year with the > intention of lengthing the support period for the next ABI version. For the record, I would prefer a v7 saying it is a fixed period of time, being one year at first and should be longer next. Please don't state "supported for one year", which can be understood as a general truth. > ABI changes that preserve ABI compatibility with the major ABI version are > permitted in subsequent releases. ABI changes, follow similar approval rules as > before with the additional gate of now requiring technical board approval. The > merging and release of ABI breaking changes would now be pushed to the > declaration of the next major ABI version. > > This change encourages developers to maintain ABI compatibility with the major > ABI version, by promoting a permissive culture around those changes that > preserve ABI compatibility. This approach begins to align DPDK with those > projects that declare major ABI versions (e.g. version 2.x, 3.x) and support > those versions for some period, typically two years or more. > > To provide an example of how this might work in practice: > > * 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. OK I agree with these explanations.