From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 7B132378B for ; Thu, 28 Jul 2016 14:55:55 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 28 Jul 2016 05:55:56 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,434,1464678000"; d="scan'208";a="1004173926" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by orsmga001.jf.intel.com with ESMTP; 28 Jul 2016 05:55:53 -0700 Date: Thu, 28 Jul 2016 21:01:14 +0800 From: Yuanhan Liu To: "Mcnamara, John" Cc: "dev@dpdk.org" Message-ID: <20160728130114.GB30752@yliu-dev.sh.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] DPDK Stable Releases and Long Term Support 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: Thu, 28 Jul 2016 12:55:55 -0000 On Thu, Jul 28, 2016 at 12:33:18PM +0000, Mcnamara, John wrote: > Initial Stable Release > ---------------------- > > The initial DPDK Stable Release will be 16.07. It will be viewed as a trial of > the Stable Release/LTS policy to determine what are the best working practices > for DPDK. > > The maintainer for the initial release will be Yuanhan Liu > . It is hoped that other community members will > volunteer as maintainers for other Stable Releases. > > The initial targeted release for LTS is proposed to be 16.11 based on the > results of the work carried out on the 16.07 Stable Release. > > A list has been set up for Stable Release/LTS specific discussions: > . This address can also be used for CCing maintainers on bug > fix submissions. Yes, we could use this mailing list for that. But it's slightly different from what I proposed in the first time: For each bug fix patch that need be backported to a stable branch, it's suggested to add following line in the commit log, just before your Signed-off-by: Cc: So that this patch will be cc'ed to the stable mailing list; this is an explicit sign to tell the stable maintainers, "hey, there is a candidate for a stable release. Please review and consider merge it". If we have several stable branches later and a patch just applies to a specific branch, it could be: Cc: v16.07 And we should doc this at page http://dpdk.org/dev. --yliu