From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: claim v16.07 as a stable release
Date: Tue, 6 Sep 2016 15:12:54 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2025F1593@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20160906122348.GA13070@yliu-dev.sh.intel.com>
> -----Original Message-----
> From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com]
> Sent: Tuesday, September 6, 2016 1:24 PM
> To: dev@dpdk.org
> Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; Mcnamara, John
> <john.mcnamara@intel.com>
> Subject: Re: [PATCH] maintainers: claim v16.07 as a stable release
>
> 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:
Hi Yuanhan,
That is good news. :-)
> 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).
That is a good idea. Perhaps it could be a new Contributors Guide or a new section in the "Contributing Code to DPDK" doc.
John
prev parent reply other threads:[~2016-09-06 15:12 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
2016-09-06 15:12 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE2025F1593@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=yuanhan.liu@linux.intel.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).