Re: [dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap

[Thomas Monjalon <thomas@monjalon.net>]

09/03/2018 15:03, Ananyev, Konstantin:
> From: Thomas Monjalon
> > 09/03/2018 14:44, Luca Boccassi:
> > > On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote:
> > > > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > > >
> > > > ---
> > > > This is at the same time, a call for volunteer,
> > > > and a proposed change to shorten the wait for the first stable
> > > > releases
> > > > from at least 3 months to 2 months.
> > > >
> > > > Let's add this discussion to the agenda of the next techboard
> > > > meeting.
> > >
> > > The issue is how to decide what goes into a stable release, if it does
> > > not follow a main release.
> > >
> > > Right now we follow the main release as that means there is a list of
> > > accepted and merged commits that can be backported - if the stable
> > > release is anticipated, what is going to be backported?
> > 
> > If we pull patches more regularly in master, there can be a lot of fixes
> > accumulated during 2 months.
> 
> But these patches need to be properly tested before going into LTS, right?
> So it means extra effort for the validation teams?

Exact
The stable release must be validated anyway.
The proposal is to validate the .1 release before starting RC1 validation,
instead of doing it after the .0 release.