DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	bluca@debian.org, nhorman@tuxdriver.com
Subject: Re: [dpdk-dev] Process for removing __rte_experimental
Date: Fri, 25 May 2018 11:49:48 +0200	[thread overview]
Message-ID: <1548019.9fvx9bZ0Lj@xps> (raw)
In-Reply-To: <3ce83a95-8fa0-dfdd-978d-29c5c439a10c@nxp.com>

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)
> 

  reply	other threads:[~2018-05-25  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25  9:35 Shreyansh Jain
2018-05-25  9:49 ` Thomas Monjalon [this message]
2018-05-25 10:17   ` Luca Boccassi
2018-05-25 11:16     ` Shreyansh Jain
2018-05-25 11:23 ` Neil Horman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1548019.9fvx9bZ0Lj@xps \
    --to=thomas@monjalon.net \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=nhorman@tuxdriver.com \
    --cc=shreyansh.jain@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).