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 19BFD2A5E for ; Fri, 24 Feb 2017 11:42:58 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga105.jf.intel.com with ESMTP; 24 Feb 2017 02:42:57 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,200,1484035200"; d="scan'208";a="827996833" Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by FMSMGA003.fm.intel.com with ESMTP; 24 Feb 2017 02:42:56 -0800 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.77]) by IRSMSX107.ger.corp.intel.com ([169.254.10.3]) with mapi id 14.03.0248.002; Fri, 24 Feb 2017 10:42:55 +0000 From: "Mcnamara, John" To: Thomas Monjalon , Yuanhan Liu CC: "web@dpdk.org" , "Liu, Yu Y" Thread-Topic: [PATCH] add stable and LTS release plan Thread-Index: AQHSdXFz5Oj8EOoBbkq5yRXenFIo56F4HoSAgAAHDDA= Date: Fri, 24 Feb 2017 10:42:55 +0000 Message-ID: References: <1485173446-30737-1-git-send-email-yuanhan.liu@linux.intel.com> <2123589.QQF2zxEr9x@xps13> In-Reply-To: <2123589.QQF2zxEr9x@xps13> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNDk0YjFjNTktYzI5Yy00YmI5LWJkMmUtNmJmYmVlOTljMDE1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjQ5ZHVcL1BxbzdoaGc1Z1F3aWNkdVFkU3NIRlZ3eUlKU3Q4bDUzR2NPeWFvPSJ9 x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Fri, 24 Feb 2017 10:42:59 -0000 > -----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 >=20 > Hi, >=20 > Sorry there was no feedback on this patch. >=20 > 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. >=20 > It is merged: http://dpdk.org/doc/guides/contributing/stable.html >=20 > > +

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. >=20 > 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=20 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.=20 For an LTS release, which has a longer maintenance period (2 years) there will be several releases (.2, .3, etc.). >=20 > >

Scheduling

>=20 > 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.