From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <bluca@debian.org>
Cc: web@dpdk.org, yliu@fridaylinux.org, ktraynor@redhat.com,
techboard@dpdk.org
Subject: Re: [dpdk-web] [PATCH] update stable releases roadmap
Date: Fri, 09 Mar 2018 14:49:27 +0100 [thread overview]
Message-ID: <5601805.V4YcVmhU8q@xps> (raw)
In-Reply-To: <1520603091.5685.8.camel@debian.org>
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.
next prev parent reply other threads:[~2018-03-09 13:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 13:36 Thomas Monjalon
2018-03-09 13:44 ` Luca Boccassi
2018-03-09 13:49 ` Thomas Monjalon [this message]
2018-03-09 14:03 ` [dpdk-web] [dpdk-techboard] " Ananyev, Konstantin
2018-03-09 14:19 ` Thomas Monjalon
2018-03-09 15:24 ` Ferruh Yigit
2018-03-09 15:45 ` Thomas Monjalon
2018-03-09 17:30 ` Luca Boccassi
2018-03-09 14:30 ` [dpdk-web] " Kevin Traynor
2018-03-09 14:51 ` Thomas Monjalon
2018-03-09 15:43 ` Kevin Traynor
2018-03-22 11:03 ` Luca Boccassi
2018-03-22 11:22 ` Luca Boccassi
2018-03-22 11:25 ` Thomas Monjalon
[not found] ` <1522937784.16877.28.camel@debian.org>
2018-04-05 14:19 ` Christian Ehrhardt
2018-04-05 14:23 ` Thomas Monjalon
2018-04-10 23:28 ` [dpdk-web] [PATCH v2] " Thomas Monjalon
2018-04-11 10:04 ` Luca Boccassi
2018-04-11 10:43 ` Christian Ehrhardt
2018-04-11 15:10 ` Kevin Traynor
2018-04-18 9:05 ` Ferruh Yigit
2018-04-18 9:14 ` Thomas Monjalon
2018-04-18 12:28 ` Ferruh Yigit
2018-04-18 13:28 ` Thomas Monjalon
2018-04-19 9:38 ` Kevin Traynor
2018-04-20 15:52 ` [dpdk-web] [dpdk-dev] " Aaron Conole
2018-04-25 8:33 ` Ferruh Yigit
2018-04-25 10:03 ` Luca Boccassi
2018-04-30 10:47 ` Thomas Monjalon
2018-05-01 14:16 ` Aaron Conole
2018-05-01 15:46 ` Kevin Traynor
2018-05-01 16:02 ` Thomas Monjalon
2018-05-17 16:32 ` [dpdk-web] [PATCH v3] " Thomas Monjalon
2018-05-17 16:41 ` Ferruh Yigit
2018-05-17 16:59 ` Thomas Monjalon
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=5601805.V4YcVmhU8q@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=ktraynor@redhat.com \
--cc=techboard@dpdk.org \
--cc=web@dpdk.org \
--cc=yliu@fridaylinux.org \
/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).