Re: [dpdk-dev] [dpdk-techboard] [PATCH] doc: scheduler API deprecation notice

[Stephen Hemminger <stephen@networkplumber.org>]

On Wed, 12 Aug 2020 14:23:51 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:

> 12/08/2020 12:57, Hemant Agrawal:
> > > -----Original Message-----
> > > From: techboard <techboard-bounces@dpdk.org> On Behalf Of Maxime
> > > Coquelin
> > > 
> > > On 8/12/20 12:22 PM, Thomas Monjalon wrote:  
> > > > 12/08/2020 11:52, Bruce Richardson:  
> > > >> 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! :-)  
> > > >
> > > > I agree
> > > >
> > > > We need more opinions from other techboard members to make it a  
> > > decision.  
> > > >
> > > >  
> > > 
> > > I agree too, let's give a bit more flexibility for the deprecation notice.
> > > 
> > > Maxime  
> > 
> > +1
> > Hemant  
> 
> I've applied the patch after 20.11-rc0.

I am ok with changing this for 20.11 since there aren't a lot of users of
this subsystem and the change should be API compatiable