From: Ray Kinsella <mdr@ashroe.eu>
To: Nithin Dabilpuram <nithind1988@gmail.com>,
ferruh.yigit@intel.com, bruce.richardson@intel.com,
cristian.dumitrescu@intel.com, thomas@monjalon.net,
bluca@debian.org, jasvinder.singh@intel.com,
arybchenko@solarflare.com, ray.kinsella@intel.com,
nhorman@tuxdriver.com, ktraynor@redhat.com,
david.marchand@redhat.com,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, jerinj@marvell.com, kkanas@marvell.com,
Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] doc: deprication notice to mark tm spec as experimental
Date: Tue, 5 May 2020 07:47:43 +0100 [thread overview]
Message-ID: <11475594-5c38-d65c-332e-78342241d486@ashroe.eu> (raw)
In-Reply-To: <20200501171622.23410-1-nithind1988@gmail.com>
On 01/05/2020 18:16, Nithin Dabilpuram wrote:
> From: Nithin Dabilpuram <ndabilpuram@marvell.com>
>
> Based on the discussion in below mail thread, it is concluded that
> all traffic manager API's (rte_tm.h) need to be marked experimental
> till few more releases to support further improvements to spec.
>
> https://mails.dpdk.org/archives/dev/2020-April/164970.html
>
> Adding deprication notice for the same in advance.
>
> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 1339f54..8c90ec9 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -118,3 +118,12 @@ Deprecation Notices
> Python 2 support will be completely removed in 20.11.
> In 20.08, explicit deprecation warnings will be displayed when running
> scripts with Python 2.
> +
> +* traffic manager: Based on the discussion in the thread
> + https://mails.dpdk.org/archives/dev/2020-April/164970.html it turns out that
> + all traffic manager API's in ``rte_tm.h`` were mistakenly made stable even
> + though the MAINTAINER's file and header file text mentions it to be still
> + experimental. Given that even now, both the maintainer and other contributor's
> + are inclined towards keeping those API's in experimental state till some more
> + releases in support of spec improvements, it is decided that all API's in
> + ``rte_tm.h`` will be marked back as experimental in v20.11 DPDK release.
>
Slightly wordy - suggest making it a small bit more concise as follows.
* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly made
abi stable in the v19.11 release. The TM maintainer and other contributor's have
agreed to keep the TM API's as experimental in expectation of additional spec
improvements. Therefore, all API's in ``rte_tm.h`` will be marked back as
experimental in v20.11 DPDK release. For more detail, please see `the thread
<https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
Ray K
next prev parent reply other threads:[~2020-05-05 6:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 17:16 Nithin Dabilpuram
2020-05-05 6:47 ` Ray Kinsella [this message]
2020-05-05 7:45 ` [dpdk-dev] [EXT] " Nithin Dabilpuram
2020-05-05 8:07 ` [dpdk-dev] [PATCH v2] " Nithin Dabilpuram
2020-05-05 8:10 ` Ray Kinsella
2020-05-05 8:55 ` Dumitrescu, Cristian
2020-05-21 10:49 ` Jerin Jacob
2020-05-24 20:58 ` Nithin Kumar D
2020-05-24 23:33 ` Thomas Monjalon
2020-09-09 17:22 ` [dpdk-dev] [PATCH] ethdev: mark all traffic manager API " Nithin Dabilpuram
2020-09-09 17:49 ` Dumitrescu, Cristian
2020-09-09 18:23 ` Ferruh Yigit
2020-09-10 8:05 ` [dpdk-dev] [PATCH v2] " Nithin Dabilpuram
2020-09-10 8:30 ` Kinsella, Ray
2020-09-10 10:56 ` [dpdk-dev] [EXT] " Nithin Dabilpuram
2020-09-10 11:01 ` Kinsella, Ray
2020-09-10 11:22 ` Nithin Dabilpuram
2020-09-10 8:36 ` [dpdk-dev] " Ferruh Yigit
2020-09-10 8:37 ` Dumitrescu, Cristian
2020-09-10 9:54 ` [dpdk-dev] [EXT] " Nithin Dabilpuram
2020-09-10 9:51 ` [dpdk-dev] [EXT] " Nithin Dabilpuram
2020-09-10 10:09 ` [dpdk-dev] [PATCH v3] " Nithin Dabilpuram
2020-09-10 11:34 ` Ferruh Yigit
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=11475594-5c38-d65c-332e-78342241d486@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=arybchenko@solarflare.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=kkanas@marvell.com \
--cc=ktraynor@redhat.com \
--cc=marko.kovacevic@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=nhorman@tuxdriver.com \
--cc=nithind1988@gmail.com \
--cc=ray.kinsella@intel.com \
--cc=thomas@monjalon.net \
/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).