From: Thomas Monjalon <thomas@monjalon.net>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 18/06/2020
Date: Thu, 18 Jun 2020 17:30:52 +0200 [thread overview]
Message-ID: <2141362.8UMlx2o4W2@thomas> (raw)
In-Reply-To: <534ad524-4fd3-a1a2-2de9-16322b5220a5@intel.com>
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.
prev parent reply other threads:[~2020-06-18 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 10:26 Ferruh Yigit
2020-06-18 14:09 ` Trahe, Fiona
2020-06-18 15:26 ` Ferruh Yigit
2020-06-18 15:30 ` Thomas Monjalon [this message]
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=2141362.8UMlx2o4W2@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=john.mcnamara@intel.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).