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 EC98BA04F1; Thu, 18 Jun 2020 17:31:01 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D6CFA1BF84; Thu, 18 Jun 2020 17:31:00 +0200 (CEST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by dpdk.org (Postfix) with ESMTP id 267011BF57 for ; Thu, 18 Jun 2020 17:30:59 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 6543E95D; Thu, 18 Jun 2020 11:30:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Thu, 18 Jun 2020 11:30:55 -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= hZe0pNEhpKle75gbdIuAobKzzw2BA/l4MYx44DTGLKM=; b=NY+v2lbz1hzdNp4O Y6mNTGArecAAkqWbXF9XOPVNsp3jUZVsuMD1OYmQ2jOcEsoXKWtQPUuQXC61Rm8y trpCyvFMh4pNvTgafPW2si/yYQ5qBDFpPtQbE1WTqNS6oqixoTHdLKvxUW6zWD5h 1OQPGvhsbnS4aSFSVz4oCTgJ8KewwK5DeYwABcudH+wEnyGp1Z6DwQ9D4BvGVJ17 OvTbxJlT7H8pL0SDHldZvj5c0TZHnz6s8zn/HC3+ACQvlGRysLtqlCun4K67zdaV yQuiBRvcTmSaQsQj5YmBDq0hQH5upukXjHv/nj4V8hAlHXNqSA4E+dU4FZki2gQa Yu0EVQ== 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=fm3; bh=hZe0pNEhpKle75gbdIuAobKzzw2BA/l4MYx44DTGL KM=; b=ucFRObPp4SQjvq1ZKmRUTc8mUlz13TYDVyc1iCRWGbqrhfzM9PgivH++6 mUEYPDZfySP1C+lOoiD6V0+zhLASjhWeV1wnyG0e2W94iWxC0ePhEQhl9JeeNFSZ gv83BVDA5Hz8LlfrrbJewic/A8Gv4hk/9L/8fJIFFHD8Ht59mSlByAtudaXfSarL q0YkAUgEUJXI+VZ6htrzYvbPhhGIyowklG+9Iac9ylhZQIPJq14nQWU5HQtoJg8a GhJJaUpBRCgpPZiEhwPmnGy9bYkcX1emAR858PF1fzxdvr5ZV48pe/ysW3yKBW/G /XNW3oMu6N8y2CQoFm4gu1bcCfibQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudejgedgledtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght 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 009C530614FA; Thu, 18 Jun 2020 11:30:53 -0400 (EDT) From: Thomas Monjalon To: "Trahe, Fiona" , Ferruh Yigit Cc: "dev@dpdk.org" , "Mcnamara, John" Date: Thu, 18 Jun 2020 17:30:52 +0200 Message-ID: <2141362.8UMlx2o4W2@thomas> In-Reply-To: <534ad524-4fd3-a1a2-2de9-16322b5220a5@intel.com> References: <534ad524-4fd3-a1a2-2de9-16322b5220a5@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] DPDK Release Status Meeting 18/06/2020 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" 18/06/2020 17:26, Ferruh Yigit: > On 6/18/2020 3:09 PM, Trahe, Fiona wrote: > > Hi all, > > > > If there's a cryptodev API change planned for 20.11 (an ABI breakage), is it necessary > > to send a deprecation notice in 20.08? > > Or can this just be worked during the normal 20.11 patch review cycle? > > As far as I got it, it needs to follow the regular deprecation process. Which is > deprecation notice should be sent and merged (with 3 acks) in 20.08, so that it > can be changed in 20.11. > > It can be good to highlight this, perhaps in next release status meeting, since > there may be some ABI changes waiting for 20.11, this release is last change for > them to send a deprecation notice. Yes Good idea to highlight it.