From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 749272BAA; Tue, 28 Feb 2017 08:14:07 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga105.jf.intel.com with ESMTP; 27 Feb 2017 23:14:06 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,218,1484035200"; d="scan'208";a="1103066419" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by orsmga001.jf.intel.com with ESMTP; 27 Feb 2017 23:14:05 -0800 Date: Tue, 28 Feb 2017 15:13:00 +0800 From: Yuanhan Liu To: Thomas Monjalon Cc: John McNamara , dev@dpdk.org, stable@dpdk.org Message-ID: <20170228071300.GO18844@yliu-dev.sh.intel.com> References: <20170120084330.GY9046@yliu-dev.sh.intel.com> <1841036.sU38etbx4S@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1841036.sU38etbx4S@xps13> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v1] doc: add guidelines on stable and lts releases X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 07:14:08 -0000 On Wed, Feb 08, 2017 at 06:39:23AM -0800, Thomas Monjalon wrote: > 2017-01-20 16:43, Yuanhan Liu: > > 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. > > OK, thanks Yuanhan. > > Have you received any proposal to help or maintain a future stable branch? Nope, and I think I need help here. Since v17.02, I have to maintain two stable releases for each cycle, which is a bit burden to me. I would appreciate if anyone has interest in maintain the stable releases while I'm focusing on the LTS release. I have made most of the work automatic (I wrote quite few scripts to help myself). It should not be a tough task for anyone volunteering this task. --yliu