From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 88AB311F5 for ; Tue, 15 Dec 2015 14:38:01 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga102.fm.intel.com with ESMTP; 15 Dec 2015 05:38:00 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,432,1444719600"; d="scan'208";a="13524230" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by fmsmga004.fm.intel.com with ESMTP; 15 Dec 2015 05:37:59 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.23]) by IRSMSX104.ger.corp.intel.com ([169.254.5.138]) with mapi id 14.03.0248.002; Tue, 15 Dec 2015 13:37:58 +0000 From: "O'Driscoll, Tim" To: Thomas Monjalon , "dev@dpdk.org" Thread-Topic: [dpdk-dev] releases scheduling Thread-Index: AQHRNdvkh0bGzE117U+VyddDUoNHdZ7MDXcw Date: Tue, 15 Dec 2015 13:37:58 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA6747CE41@IRSMSX108.ger.corp.intel.com> References: <1667533.heuKAiE6KB@xps13> In-Reply-To: <1667533.heuKAiE6KB@xps13> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMjYyNGM5ZjMtZmNlOS00NzM0LWJmNmYtZjZmMjU1Zjc5NjkxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoidHJMQkhRSm95Z2huMnlsb0dDUDRwT2tHdURRcjUrZTlnN3VDeDdoK1hUZz0ifQ== x-ctpclassification: CTP_IC 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-dev] releases scheduling 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: Tue, 15 Dec 2015 13:38:01 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Sunday, December 13, 2015 7:23 PM > To: dev@dpdk.org > Subject: [dpdk-dev] releases scheduling >=20 > Hi all, >=20 > We need to define the deadlines for the next releases. > During 2015, we were doing a release every 4 months. > If we keep the same pace, the next releases would be: > 2.3: end of March > 2.4: end of July > 2.5: end of November >=20 > However, things move fast and it may be a bit long to wait 4 months for > a feature. That's why I suggest to progressively shorten release terms: > 2.3: end of March > 2.4: mid July > 2.5: end of October > and continue with a release every 3 months: > 2.6: end of January > 2.7: end of April > 2.8: end of July > This planning would preserve some of the major holiday periods > (February, May, August, December). >=20 > The first period, for the first submission of a feature, was 2 months > long. > Then we had 2 other months to discuss, merge and fix. > We should shorten only the first period. >=20 > Anyway, the next deadlines should be unchanged: > - January 31: end of first submission phase > - March 31: release 2.3 >=20 > Opinions are welcome. I think moving to quarterly releases is a good idea. Your proposal to do th= is in a gradual way, so that we don't change the 2.3 dates, also makes sens= e. Should we consider changing the release numbering at the same time? It's di= fficult to keep track of when each 2.x release is due, and we don't have an= y criteria in place for moving to 3.x in future. Many people like the Ubunt= u numbering scheme of Year.Month. Should we consider adopting that conventi= on? If we move in future to a model where we have long-term support release= s (something that was touched on in Dublin), then we could append an LTS de= signation to the release number. Tim