From: Bruce Richardson <bruce.richardson@intel.com>
To: "Eads, Gage" <gage.eads@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Ray Kinsella <mdr@ashroe.eu>, "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
"phil.yang@arm.com" <phil.yang@arm.com>,
"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
"olivier.matz@6wind.com" <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] stack: remove experimental tag from API
Date: Thu, 28 May 2020 15:33:02 +0100 [thread overview]
Message-ID: <20200528143302.GA924@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <SN6PR11MB257480596F04D1F8203C478EF68E0@SN6PR11MB2574.namprd11.prod.outlook.com>
On Thu, May 28, 2020 at 02:18:32PM +0000, Eads, Gage wrote:
>
>
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Thursday, May 28, 2020 3:11 AM
> > To: Eads, Gage <gage.eads@intel.com>; Ray Kinsella <mdr@ashroe.eu>
> > Cc: dev@dpdk.org; david.marchand@redhat.com; nhorman@tuxdriver.com;
> > phil.yang@arm.com; honnappa.nagarahalli@arm.com;
> > olivier.matz@6wind.com
> > Subject: Re: [PATCH] stack: remove experimental tag from API
> >
> > 28/05/2020 07:46, Ray Kinsella:
> > > Hi Gage,
> > >
> > > Do you have any idea.
> > > If the change from experimental to stable symbol is likely to break anyone's
> > application?
> > > (are folks actively using the api with shared libraries)
>
> Good question. I don't have a good sense of the active users, so I'd rather play it safe.
>
> > >
> > > If so, you _may_ consider offering a temporary alias to experimental until the
> > v21 is declared at 20.11.
> > > This is entirely at your discretion, see
> > > https://doc.dpdk.org/guides/contributing/abi_versioning.html (4.3.1.4)
> >
> > Or we can wait 20.11.
> >
>
> That works. I have no urgency to get this into 20.08 in particular.
>
> > Anyway I think it deserves a comment in the release notes (API section).
> >
>
> Ok, if there are no objections then I'll re-submit this patchset in a few months and include a release notes comment.
>
Or just resubmit with a 20.11 tag on it, and then mark it as "deferred" in
patchwork, so it pops up automatically for disposition again at the end of
the 20.08 cycle?
/Bruce
next prev parent reply other threads:[~2020-05-28 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 1:04 Gage Eads
2020-05-28 5:46 ` Ray Kinsella
2020-05-28 8:10 ` Thomas Monjalon
2020-05-28 8:22 ` Ray Kinsella
2020-05-28 14:18 ` Eads, Gage
2020-05-28 14:33 ` Bruce Richardson [this message]
2020-05-28 15:04 ` [dpdk-dev] [20.11] [PATCH v2] " Gage Eads
2020-05-28 15:29 ` Thomas Monjalon
2020-09-30 18:49 ` David Marchand
2020-09-30 21:39 ` [dpdk-dev] [PATCH] " Gage Eads
2020-10-05 9:07 ` Kinsella, Ray
2020-10-05 9:53 ` Kinsella, Ray
2020-10-05 12:57 ` David Marchand
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=20200528143302.GA924@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=olivier.matz@6wind.com \
--cc=phil.yang@arm.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).