From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <tim.odriscoll@intel.com> Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id E1657728E for <dev@dpdk.org>; Thu, 22 Feb 2018 11:44:14 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Feb 2018 02:44:13 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,377,1515484800"; d="scan'208";a="177206913" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga004.jf.intel.com with ESMTP; 22 Feb 2018 02:44:12 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.9]) by IRSMSX101.ger.corp.intel.com ([169.254.1.188]) with mapi id 14.03.0319.002; Thu, 22 Feb 2018 10:44:11 +0000 From: "O'Driscoll, Tim" <tim.odriscoll@intel.com> To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org> Thread-Topic: [dpdk-dev] deadlines postponed Thread-Index: AQHTq8jCbzMnGnT7AkqOq3jpl4WJOaOwO0fg Date: Thu, 22 Feb 2018 10:44:10 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4AD1D13@IRSMSX108.ger.corp.intel.com> References: <2035733.bkODqCDiXb@xps> In-Reply-To: <2035733.bkODqCDiXb@xps> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZmQ2OGVmOTUtNWM4ZC00ZTJjLTk3Y2EtNDA5ZjI4YTM0OTcxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJ4bHVZXC9haXM2VCs5OW5Zcjg1dVh6UFBGXC9kcktmOVdnRG9FXC9yTDRpU2hnU29JZkJiUFNMRGp6UUVudVk4aGdkIn0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action 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-dev] deadlines postponed X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 22 Feb 2018 10:44:15 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Thursday, February 22, 2018 10:34 AM > To: dev@dpdk.org > Subject: [dpdk-dev] deadlines postponed >=20 > Hi, >=20 > I propose to shift the proposal deadline and the integration deadline > for 18.05: > - Proposal deadline: March 9, 2018 > - Integration deadline: April 6, 2018 > - Release: May 4, 2018 >=20 > The idea is to follow these guidelines: > - more time before the proposal deadline > - 4 weeks for integration in RC1 > - 4 weeks for bugs fixing after RC1 >=20 > You can look at this web patch for more details: > http://dpdk.org/ml/archives/web/2018-February/000580.html >=20 > Opinions? +1 At the moment, the proposal deadline is very soon after the previous releas= e. Moving this out a little would allow extra time for development, and wou= ld still keep reasonable intervals for integration and testing/bug fixing.