From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: John McNamara <john.mcnamara@intel.com>, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc: add guidelines on stable and lts releases
Date: Tue, 28 Feb 2017 15:13:00 +0800 [thread overview]
Message-ID: <20170228071300.GO18844@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1841036.sU38etbx4S@xps13>
On Wed, Feb 08, 2017 at 06:39:23AM -0800, Thomas Monjalon wrote:
> 2017-01-20 16:43, Yuanhan Liu:
> > 16.07 as a first trial of stable release, I made a proposal to have 2
> > releases: v16.07.1 shortly after v16.11-rc1 and v16.07.2 shortly after
> > v16.11. While the gap between v16.07 and v16.11 are 4 months, doing a
> > release each 2 month doesn't seem that bad. It may a bit stretch then
> > because the gap is shorter (3 months) since 16.11. Besides, the validation
> > team here are pretty busy after rc1, meaning it doesn't seem a good idea
> > to have another release shortly after that: they may quite be burdened.
> >
> > So I'm proposing to make one stable/LTS release per release cycle. For
> > example, we will have v16.11.1 shortly after v17.02, and judging that
> > v16.11 is a LTS release, we will have v16.11.2 after v17.05, and so on.
> >
> > And my plan towards a release is, I will monitor (by a script) the
> > official tree regularly (normally, weekly), and pick patches from there
> > if any to a specific stable branch. As before, an email notification will
> > be sent to the author and all email addresses mentioned in the patch
> > (normally, they are maintainers, reviewers, etc) once a patch is picked
> > as a stable candidate.
> >
> > Doing this regularly, hopefully, tells people that DPDK stable/LTS is
> > live and actively maintained.
> >
> > Any objections? If no, I could start picking patches since the beginning
> > of next week.
>
> OK, thanks Yuanhan.
>
> Have you received any proposal to help or maintain a future stable branch?
Nope, and I think I need help here. Since v17.02, I have to maintain two
stable releases for each cycle, which is a bit burden to me.
I would appreciate if anyone has interest in maintain the stable releases
while I'm focusing on the LTS release. I have made most of the work automatic
(I wrote quite few scripts to help myself). It should not be a tough task
for anyone volunteering this task.
--yliu
next prev parent reply other threads:[~2017-02-28 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 8:43 Yuanhan Liu
2017-02-08 14:39 ` Thomas Monjalon
2017-02-28 7:13 ` Yuanhan Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-13 13:06 John McNamara
2017-01-13 13:14 ` Mcnamara, John
2017-01-13 16:29 ` Thomas Monjalon
2017-01-13 17:57 ` Mcnamara, John
2017-02-08 12:24 ` 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=20170228071300.GO18844@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=stable@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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).