From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id D700BDE0 for ; Tue, 6 Sep 2016 14:11:40 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 06 Sep 2016 05:11:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,291,1470726000"; d="scan'208";a="1036031611" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by fmsmga001.fm.intel.com with ESMTP; 06 Sep 2016 05:11:39 -0700 Date: Tue, 6 Sep 2016 20:23:48 +0800 From: Yuanhan Liu To: dev@dpdk.org Cc: Thomas Monjalon , John McNamara Message-ID: <20160906122348.GA13070@yliu-dev.sh.intel.com> References: <1469708507-22231-1-git-send-email-yuanhan.liu@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1469708507-22231-1-git-send-email-yuanhan.liu@linux.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH] maintainers: claim v16.07 as a stable release X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2016 12:11:41 -0000 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 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: " 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 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 > T: git://dpdk.org/dpdk-stable > > Security Issues > -- > 1.9.0