From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"bluca@debian.org" <bluca@debian.org>,
Akhil Goyal <akhil.goyal@nxp.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: scheduler API deprecation notice
Date: Wed, 12 Aug 2020 10:52:09 +0100 [thread overview]
Message-ID: <20200812095209.GA312@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <3567036.vTBxH0KFj1@thomas>
On Mon, Aug 10, 2020 at 02:50:57PM +0200, Thomas Monjalon wrote:
> 10/08/2020 13:49, Trahe, Fiona:
> > Sorry about that Thomas, Akhil, we should have chased up acks sooner.
> >
> > Given the proposed content of the patch, and the similar changes that are recommended and agreed
> > throughout DPDK do you think an exception can be made and that this change can get into 20.11 even
> > without the deprecation notice being in 20.08?
>
> That's a question for techboard.
>
> PS: please avoid top-posting
>
My initial 2c is that we should allow this, and add the required
deprecation notice to the online docs immediately. I would assume most
people use the online docs rather than building their own from the package,
therefore adding in a deprecation notice to the online versions a few days
after a release should not be a major problem IMHO.
Also, given the fact that we have once-a-year at most to apply ABI
changes, and this is the first time we are going this, so I think a little
latitude should be given! :-)
next prev parent reply other threads:[~2020-08-12 9:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 9:41 Adam Dybkowski
2020-08-06 14:21 ` Thomas Monjalon
2020-08-06 17:18 ` Akhil Goyal
2020-08-07 22:05 ` Thomas Monjalon
2020-08-10 9:47 ` Dybkowski, AdamX
2020-08-10 10:19 ` Thomas Monjalon
2020-08-10 11:49 ` Trahe, Fiona
2020-08-10 12:50 ` Thomas Monjalon
2020-08-12 9:52 ` Bruce Richardson [this message]
2020-08-12 10:22 ` Thomas Monjalon
2020-08-12 10:49 ` [dpdk-dev] [dpdk-techboard] " Maxime Coquelin
2020-08-12 10:57 ` Hemant Agrawal
2020-08-12 12:23 ` Thomas Monjalon
2020-08-12 15:25 ` Stephen Hemminger
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=20200812095209.GA312@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=anatoly.burakov@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.mcnamara@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=stephen@networkplumber.org \
--cc=techboard@dpdk.org \
--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).