[dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap
konstantin.ananyev at intel.com
Fri Mar 9 15:03:59 CET 2018
> -----Original Message-----
> From: techboard [mailto:techboard-bounces at dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Friday, March 9, 2018 1:49 PM
> To: Luca Boccassi <bluca at debian.org>
> Cc: web at dpdk.org; yliu at fridaylinux.org; ktraynor at redhat.com; techboard at dpdk.org
> Subject: Re: [dpdk-techboard] [dpdk-web] [PATCH] update stable releases roadmap
> 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 at 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?
More information about the web