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 ABB822BB2 for ; Tue, 28 Feb 2017 08:03:35 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga105.jf.intel.com with ESMTP; 27 Feb 2017 23:03:34 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,218,1484035200"; d="scan'208";a="230479630" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by fmsmga004.fm.intel.com with ESMTP; 27 Feb 2017 23:03:32 -0800 Date: Tue, 28 Feb 2017 15:02:29 +0800 From: Yuanhan Liu To: "Mcnamara, John" Cc: Thomas Monjalon , "web@dpdk.org" , "Liu, Yu Y" Message-ID: <20170228070229.GN18844@yliu-dev.sh.intel.com> References: <1485173446-30737-1-git-send-email-yuanhan.liu@linux.intel.com> <2123589.QQF2zxEr9x@xps13> 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-web] [PATCH] add stable and LTS release plan X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 07:03:36 -0000 On Fri, Feb 24, 2017 at 10:42:55AM +0000, Mcnamara, John wrote: > > > > -----Original Message----- > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > Sent: Friday, February 24, 2017 10:00 AM > > To: Yuanhan Liu ; Mcnamara, John > > > > Cc: web@dpdk.org; Liu, Yu Y > > Subject: Re: [PATCH] add stable and LTS release plan > > > > Hi, > > > > Sorry there was no feedback on this patch. > > > > 2017-01-23 20:10, Yuanhan Liu: > > > Cc: John McNamara > > > Cc: Yu Liu > > > Signed-off-by: Yuanhan Liu > > > --- > > > > > > I made it in rush, meaning there are huge room for improvements > > > about this short update :) > > > > > > Another thought from me is to link the detailed stable/LTS doc > > > from John, when it's merged. > > > > It is merged: http://dpdk.org/doc/guides/contributing/stable.html Good. I could make a v2 to point it. > > > +

Stable and LTS release

> > > +

A new release will be made about every 3 months, shortly (about 3 > > > + weeks) after an upstream release is made. For example, v16.11.1 will > > > + be released shortly after v17.02 is released. > > > +

For a stable release, normally, there is only one such release. > > > + While for a LTS release, which has longer maintainance (2 years), > > > + there are more releases (.2, .3, etc) following. > > > > John, any opinion or rewording for this text? > > The wording id fine. The only thing is that "will be released" is in the > future tense and 16.11.1 is due to be release. So it may be better as > below. Also s/maintainance/maintenance/ > > >

Stable and LTS release

>

A new stable release will be made about every 3 months, shortly (around > 3 weeks) after an upstream release has been made. For example, v16.11.1 > was released shortly after v17.02. >

In general, there will only be one such release for a stable release. > For an LTS release, which has a longer maintenance period (2 years) > there will be several releases (.2, .3, etc.). Thanks, John! > > > > >

Scheduling

> > > > I think we should publish the dates for the next releases here. > > Agreed. Just add 3 weeks to the other release dates as a guidance. Okay. And I think we still miss one thing: we may need one new section to tell which version is a LTS. Any idea? --yliu