From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id DCF76DE5 for ; Tue, 17 Jan 2017 09:37:32 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga105.fm.intel.com with ESMTP; 17 Jan 2017 00:37:29 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,243,1477983600"; d="scan'208";a="1113783649" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga002.fm.intel.com with ESMTP; 17 Jan 2017 00:37:29 -0800 Received: from fmsmsx116.amr.corp.intel.com (10.18.116.20) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 17 Jan 2017 00:37:29 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx116.amr.corp.intel.com (10.18.116.20) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 17 Jan 2017 00:37:28 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.88]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.132]) with mapi id 14.03.0248.002; Tue, 17 Jan 2017 16:37:26 +0800 From: "Xu, Qian Q" To: Thomas Monjalon , "dev@dpdk.org" CC: "Xu, Qian Q" Thread-Topic: [dpdk-dev] delay for 17.02-rc1 Thread-Index: AQHScBIPl4eF9/stUUW7m0S0AU553aE8WHEA Date: Tue, 17 Jan 2017 08:37:25 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E3B4E8750@shsmsx102.ccr.corp.intel.com> References: <4833533.9kVdhXKYOk@xps13> In-Reply-To: <4833533.9kVdhXKYOk@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] delay for 17.02-rc1 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2017 08:37:33 -0000 Thomas For validation, we don't expect too much difference b/w RC1 and RC2. If onl= y 1-2 features gap, then it's acceptable, but if=20 too many features differences b/w RC1 and RC2, then RC1 test result may be = meaningless.=20 If some patches are ready, could we merge them to master branch ASAP, we ha= ve the daily regression test on the master branch, so we=20 can identify any new issues very quickly. If all patches merge to master in= one day, we may meet many errors that is difficult to track.=20 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Tuesday, January 17, 2017 12:03 AM > To: dev@dpdk.org > Subject: [dpdk-dev] delay for 17.02-rc1 >=20 > Hi all, >=20 > As you know, the integration deadline was on January 5th: > http://dpdk.org/dev/roadmap#dates > Unfortunately, a lot of patches are not ready yet. > There are some delays in every areas, so neither the next-* trees, nor th= e > mainline, are ready. >=20 > We cannot have too much delay because: > 1/ we must be on time for next releases > 2/ there will be holidays in China very soon >=20 > Which solutions do we have? > 1/ close 17.02 features now and frustrate everyone 2/ postpone some patch= es > to RC2 if they do not disturb validation too much 3/ hurry up >=20 > Comments are welcome