From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 190294CBB; Fri, 9 Mar 2018 15:04:04 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Mar 2018 06:04:02 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,445,1515484800"; d="scan'208";a="35959035" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga004.fm.intel.com with ESMTP; 09 Mar 2018 06:04:01 -0800 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.221]) by IRSMSX153.ger.corp.intel.com ([169.254.9.213]) with mapi id 14.03.0319.002; Fri, 9 Mar 2018 14:04:00 +0000 From: "Ananyev, Konstantin" To: Thomas Monjalon , Luca Boccassi CC: "web@dpdk.org" , "yliu@fridaylinux.org" , "ktraynor@redhat.com" , "techboard@dpdk.org" Thread-Topic: [dpdk-techboard] [dpdk-web] [PATCH] update stable releases roadmap Thread-Index: AQHTt6zc95ZmYCnPtk2+ukPzE2U1N6PH64eAgAADdFA= Date: Fri, 9 Mar 2018 14:03:59 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725890F22385@irsmsx105.ger.corp.intel.com> References: <20180309133612.19927-1-thomas@monjalon.net> <1520603091.5685.8.camel@debian.org> <5601805.V4YcVmhU8q@xps> In-Reply-To: <5601805.V4YcVmhU8q@xps> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNmY4OTAzYTEtNjgyZS00MmVhLThkOGEtNjczODlhYzk3MDYzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6InIrREl1dDNaWjhmY2s1NG9YUURYZTBlRVUrSm9ndm14VnArOHVBN0N0blE9In0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap 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, 09 Mar 2018 14:04:06 -0000 > -----Original Message----- > From: techboard [mailto:techboard-bounces@dpdk.org] On Behalf Of Thomas M= onjalon > Sent: Friday, March 9, 2018 1:49 PM > To: Luca Boccassi > Cc: web@dpdk.org; yliu@fridaylinux.org; ktraynor@redhat.com; techboard@dp= dk.org > Subject: Re: [dpdk-techboard] [dpdk-web] [PATCH] update stable releases r= oadmap >=20 > 09/03/2018 14:44, Luca Boccassi: > > On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > > > Signed-off-by: Thomas Monjalon > > > > > > --- > > > This is at the same time, a call for volunteer, > > > and a proposed change to shorten the wait for the first stable > > > releases > > > from at least 3 months to 2 months. > > > > > > Let's add this discussion to the agenda of the next techboard > > > meeting. > > > > The issue is how to decide what goes into a stable release, if it does > > not follow a main release. > > > > Right now we follow the main release as that means there is a list of > > accepted and merged commits that can be backported - if the stable > > release is anticipated, what is going to be backported? >=20 > If we pull patches more regularly in master, there can be a lot of fixes > accumulated during 2 months. But these patches need to be properly tested before going into LTS, right? So it means extra effort for the validation teams? Konstantin =20