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 3EC6BA0588; Tue, 21 Apr 2020 11:36:28 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 97C5C1D146; Tue, 21 Apr 2020 11:36:27 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id A58221C43E for ; Tue, 21 Apr 2020 11:36:26 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 4075C5C00C0; Tue, 21 Apr 2020 05:36:26 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Tue, 21 Apr 2020 05:36:26 -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=fm1; bh= M8H6RAGXhiv4gnA/VOCiajQTvX/fGfX5u4iJ5JGaJeA=; b=WRsHBX/8vdDw11PI V5hVxvcETn61B4Mhqj834Nj/a5mzNALoOSNxjMKGGpIM8PmaRdSa0wQbj5ZAIP56 dNR7uJYIK+ckzTj0+126w512dvgkBFn4M43JFN09Vpdw7xg8zwTOrRRdB3vNEcag tfXY2hXoudRlqE1BiMN3/x0uX8XZLV0XFa6WarHlraq2bSFOEjX3yCB+DfYadQvQ RRhOsNSwpSP2eFrpsuqMYF1xiYukyNwTvDM+kHg6V8HR2Qrkc4/RYDN9lYx9tito ffVasAeTWSSFz2KvO1GWwYpfXDQ3ydhxD59Dw/0nl2rKqofC0aimPhjXS7YzdzfJ 74W9ZA== 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=fm2; bh=M8H6RAGXhiv4gnA/VOCiajQTvX/fGfX5u4iJ5JGaJ eA=; b=KHTcd6+xchn0bOF9sTdnla76VPBeEiqZCCf5i4o8OWCuQIQwMsOF/HT5C uYsMqLHqSnhWAX3OBOYndD+PbECkB3bl08s07hldOH5d9vKv7q411VMZOHX0mC7O 53GmOuk30ED+UjjmoDlwIpctpTaw6H5F9BiWwp5vdyrwXRxtbKfdHf7F7C26gJxy x8UC4R0iNVDcN7Ba2TaHb73+/mz0bfzDTdxQtHQEeUZYxpRsvWt8G/WaWm9t49q+ 94/a1iE2AsFdNL1eJKsJQGQHty1hZviEBmUAVRbTaU638l8+vb+VU2GjpVE+ad+K jyigYEWleH+mgF1433hn4xC2Eh1EA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrgeehgddujecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth 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 1DDA83065C64; Tue, 21 Apr 2020 05:36:22 -0400 (EDT) From: Thomas Monjalon To: Ray Kinsella Cc: "Trahe, Fiona" , "Richardson, Bruce" , "dev@dpdk.org" , "Kusztal, ArkadiuszX" , Neil Horman , Luca Boccassi , Kevin Traynor , "Yigit, Ferruh" , Akhil Goyal Date: Tue, 21 Apr 2020 11:36:21 +0200 Message-ID: <3221115.QJadu78ljV@thomas> In-Reply-To: <27c97b09-0b78-ccbc-db1e-860ac6012aec@ashroe.eu> References: <20200318204136.10508-1-arkadiuszx.kusztal@intel.com> <3812780.yFuDdFVEAc@thomas> <27c97b09-0b78-ccbc-db1e-860ac6012aec@ashroe.eu> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] cryptodev: version rte_cryptodev_info_get function 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" 21/04/2020 08:01, Ray Kinsella: > > On 20/04/2020 18:37, Thomas Monjalon wrote: > > 20/04/2020 19:31, Ray Kinsella: > >> > >> Our only commitment is to the stability of the v19.11/v20 ABI, until v21. > >> > >> That said, once an ABI migrates from EXPERIMENTAL to v21, it _shouldn't_ be changing. > >> We don't have a strict commitment to the v21 ABI until v20.11. > >> > >> However if v21 is changing across quarterlies (outside of additions) ... something else is wrong. > > > > The only way to check a symbol is not changing in a quarterly release > > is to test it. That's what we wanted to enforce: > > compare 20.02 ABI in 20.05 release. > > > > What other process do you suggest? > > > > Well I guess it's understanding the reason why you are doing something. > I can see reasons for wanting to test against both v19.11 and v20.02. > > v19.11 because our strict commitment is to the v20 abi. > v20.02 to ensure that v21 symbols are not changing between quarterly releases. > > On v20, since you tested v20.02 against v19.11 during the v20.02 release cycle. > The v20 symbols should not have changed during the v20.02 release cycle. > > I take your point, that then testing v20.05 against v20.02 would catch both v20 and v21 changes. OK, so we need a policy or process update to make this conclusion clear to everybody.