From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: John McNamara <john.mcnamara@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v1] doc: add guidelines on stable and lts releases
Date: Fri, 20 Jan 2017 16:43:30 +0800 [thread overview]
Message-ID: <20170120084330.GY9046@yliu-dev.sh.intel.com> (raw)
On Fri, Jan 13, 2017 at 01:06:22PM +0000, John McNamara wrote:
> Add document explaining the current Stable and LTS process.
John, great doc! Thanks.
Here I got one more thing to discuss about the stable release: the release
cycle. (I may better start a new thread, but I hope it would be a short
discussion, so I didn't bother with that).
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.
Thanks.
--yliu
next reply other threads:[~2017-01-20 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 8:43 Yuanhan Liu [this message]
2017-02-08 14:39 ` Thomas Monjalon
2017-02-28 7:13 ` Yuanhan Liu
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=20170120084330.GY9046@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).