From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
John McNamara <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: claim v16.07 as a stable release
Date: Tue, 6 Sep 2016 20:23:48 +0800 [thread overview]
Message-ID: <20160906122348.GA13070@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1469708507-22231-1-git-send-email-yuanhan.liu@linux.intel.com>
On Thu, Jul 28, 2016 at 08:21:47PM +0800, Yuanhan Liu wrote:
> Claim v16.07 as a stable release: only bug fix patches are allowed.
> And volunteer to be the maintainer.
>
> Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Hi all,
I will apply this patch shortly; this would literally mean I'm about
to start applying bug fixing patches to 16.07 stable branch:
git://dpdk.org/dpdk-stable 16.07
And here is the web interface: http://dpdk.org/browse/dpdk-stable/
Besides that, here I wrote some short notes about some simple rules
applies to bug fixing patches, as well as a rough release plan I made.
This is to prvoide some rough ideas to developers/contributors on how
the stable release is gonna work.
And here you go (I may make it into the DPDK doc).
--yliu
---
Some simple rules
=================
- Only bug fixes patches are allowed.
- The patch should be minimum that it just fixes a bug; anything
else (e.g. code refactoring, performance tunning) is not allowed.
This is to reduce the chance that a bug fix patch introduces
yet another bug.
- If a patch is apply-able to upstream, it will not be applied
to the stable branch until it's applied to upstream.
- You should put "Cc: <stable@dpdk.org>" in your commit log, just
before your Signed-off-by.
This is for telling the stable tree maintainer(s), "hey, here is
a patch for stable branch, please consider applying it".
Maintainers, since this is the first trial of DPDK stable release,
not all contributors know this rule. If he doesn't do that, please
help cc to <stable@dpdk.org> while you ACK/comment it. Also, please
educate him and ask him to do that in future.
About releases
==============
I plan to do (at least) 2 releases for this stable release.
One is shortly after v16.11-rc1 is out, with the mind that most of those
bug fix patches (that are apply-able to upstream) are already applied.
Another one is shortly after v16.11 is out, with the mind that the rest
bug fix patches are applied.
> ---
> MAINTAINERS | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d099131..1a5b047 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -30,8 +30,9 @@ F: scripts/checkpatches.sh
> F: scripts/load-devel-config.sh
> F: scripts/test-build.sh
>
> -Stable Branches
> ----------------
> +Stable Branch 16.07
> +-------------------
> +M: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> T: git://dpdk.org/dpdk-stable
>
> Security Issues
> --
> 1.9.0
next prev parent reply other threads:[~2016-09-06 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 12:21 Yuanhan Liu
2016-09-06 12:23 ` Yuanhan Liu [this message]
2016-09-06 15:12 ` Mcnamara, John
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=20160906122348.GA13070@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--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).