From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 1C1BE239 for ; Fri, 25 May 2018 11:50:57 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 99C0D22CF2; Fri, 25 May 2018 05:50:57 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 25 May 2018 05:50:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=AMf1EF9rQLA0vim1isead0Nf1b ZkQOuebprF//OaOaw=; b=nZXwKZbBwE1nAVAK3eAjMm0YmQ99I+ip+HyEWYFpt+ KCT/4iMr2LJY499ZFj9/dbJbSO/ji0y1pGXUnXBqaRipOQutQ2kjutjzriUoBWH5 9oMGVdFA7oqeeNKFCzrQaEJz1b/BsApOpq4EwDnaLbvHzTt5RQGFWLHypzKHIfM7 4= 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-sender:x-me-sender:x-sasl-enc; s=fm2; bh=AMf1EF 9rQLA0vim1isead0Nf1bZkQOuebprF//OaOaw=; b=aT1bTiTNOTS8+Qymx1cCKC 8KCzFulKkgSRWvKJvWL2ZWwUK8cZXK3AD8DtGyWVAqhLIjTJ+pnGFP9E9bxgdz42 Wqelf42siIYcrWLYAkbmFEDeqfkaMhlmCxE78UwAPEghDAtawtMi1SNq4+xDcBoh ug2ZnO8qtHIVdMZhChsZNP/iiyN5Bo+8va0rmYSCz6Nrwr5qxeS5gFXDczv/kbrF ZqIyPTAf0pQxiTeFRkkXlYmLy+WWRmxNtQSyFpKxbpxgoDOvJVw5juTPotVFKHXy CueP0y3pYsyVO/c21iMQ4rOMcWT1r96N1NicJhOP/n/4z99byfMAF5ESWUJiw/Yg == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (51.41.136.77.rev.sfr.net [77.136.41.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 23AF610370; Fri, 25 May 2018 05:50:55 -0400 (EDT) From: Thomas Monjalon To: Shreyansh Jain Cc: "dev@dpdk.org" , Ferruh Yigit , bluca@debian.org, nhorman@tuxdriver.com Date: Fri, 25 May 2018 11:49:48 +0200 Message-ID: <1548019.9fvx9bZ0Lj@xps> In-Reply-To: <3ce83a95-8fa0-dfdd-978d-29c5c439a10c@nxp.com> References: <3ce83a95-8fa0-dfdd-978d-29c5c439a10c@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Process for removing __rte_experimental 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: , X-List-Received-Date: Fri, 25 May 2018 09:50:58 -0000 25/05/2018 11:35, Shreyansh Jain: > While reading through [1], I couldn't understand if __rte_experimental > and EXPERIMENTAL tag removed from code and map file, respectively, are > categorized under ABI breakage or not. Thus, whether deprecation for > them should be sent or not in a release cycle for removal in subsequent > release. > > Logically, EXPERIMENTAL APIs are not part of stable APIs/ABIs and hence > they don't really break an ABI. Thus, deprecation for them doesn't make > sense. (or, as Luca noted on IRC, removing experimental is like > de-deprecation :) ) I agree, no need for prior notice, in my opinion. > On IRC, Luca pointed out that in one of the Tech Board meeting minutes > [2], this was recorded but that too has slight ambiguity to it. > > Any thoughts on this? Or, was this documented somewhere other than [1]? > > [1] http://dpdk.org/doc/guides/contributing/versioning.html > [2] https://dpdk.org/ml/archives/dev/2017-October/079961.html (Section 2-b) >