From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4A5FFA04FF; Tue, 22 Mar 2022 11:35:26 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 33BDA40E64; Tue, 22 Mar 2022 11:35:26 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 19DC740151 for ; Tue, 22 Mar 2022 11:35:25 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 809C45C010C; Tue, 22 Mar 2022 06:35:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 22 Mar 2022 06:35:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; bh=upY71hN4b1bxMf D/EayOFtgzO+Cz1KqYB8MuFL4LRE8=; b=Uwu4Nw0aa7wqOuQoTdUmJBZB9J2JrH qi0ipONYgTHqPUaQw5wSSp0rO+KzOoZD7IjN+3VccFEQWRUsD072xscrYfco2ZgN LTEjTvauTyNgh8KcblhtuJnz+isLf5v65kslmTfqV9SpvXoQlJfdRpoCAhc6eWsW 3N3DCxXSMtHgtjbGGlzPQ9BwOwN5+bIfXyuaGVqs6EoWg5WJRSIBB3qVRs/pSwun I89XbzB+tbbVkCXEMpwsryLSMCxTrS1VKR3o576gZ8kRo+DZBzhz5iyKvKJrqdGW +I2u+vQBUotvoLvscvT//UcOIvol24LMEMgR7TUzCDX6AlHpPyetF/Dw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=upY71hN4b1bxMfD/EayOFtgzO+Cz1KqYB8MuFL4LR E8=; b=n/PLKY1Rj8up9onhOWBRD1nJXQvcwYObd5fx/HKDubdDTd7klrlndwZgI wg5q9aRgldnQrBpjHJJ3ty+kIyu6akdqC9asKyz+Vfn/qoeoj6BtcYJ04RsNt59H BjWPHij+CYtGHS13XjWTH++h/gDINPpc+Q1lCz4LhU/WHgHpOFHh0mcCBNewVavu cOs1KIV003roD+IozDaB+zY1n8vv66x9KkPom0r2M4OtZxCIHzRaIrSaPDDvBWVT fAkYWtimH/VtcQbdFPf3jXpyrDHQEctlptj4nViaT58Mlf2OMduOdjwkHxBP9svX PwCzLopDncNMR2NBWOn/CQvgzhL6g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudeghedgudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepffdvffejueetleefieeludduuefgteejleevfeekjeefieegheet ffdvkeefgedunecuffhomhgrihhnpeguphgukhdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhn rdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 22 Mar 2022 06:35:23 -0400 (EDT) From: Thomas Monjalon To: David Marchand , Ray Kinsella Cc: dev , Aaron Conole , Michael Santana Subject: Re: [PATCH] version: 22.07-rc0 Date: Tue, 22 Mar 2022 11:35:21 +0100 Message-ID: <1811102.tdWV9SEqCh@thomas> In-Reply-To: <87v8w6qret.fsf@mdr78.vserver.site> References: <20220318143508.28550-1-david.marchand@redhat.com> <87v8w6qret.fsf@mdr78.vserver.site> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 22/03/2022 10:15, Ray Kinsella: > David Marchand writes: > > On Mon, Mar 21, 2022 at 2:01 PM Thomas Monjalon wrote: > >> 18/03/2022 15:35, David Marchand: > >> > +* No ABI change that would break compatibility with 21.11. > >> > >> Should we say 21.11 and 22.03? > > > > In practice, compatibility is probably maintained, but we are > > committed to maintain ABI compatibility with v21.11 only. > > So I would leave this as is. > > > > http://inbox.dpdk.org/dev/27c97b09-0b78-ccbc-db1e-860ac6012aec@ashroe.eu/ > > Agreed +1 - our only commitment is to v21.11. > Otherwise things would start to get very complicated. :-) I don't think it would be more complicated. In reality, we are already testing compatibility with minor versions, and there is no issue.