From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [dpdk-announce] DPDK 16.11 released Date: Thu, 17 Nov 2016 17:01:43 +0100 Message-ID: <2542149.maapeWSFuo@xps13> References: <3980631.9YyyMl1DK9@xps13> <1609004.OL7hRRQnMz@xps13> <82F45D86ADE5454A95A89742C8D1410E3925F412@shsmsx102.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: "Liu, Yong" , dev@dpdk.org To: "Xu, Qian Q" Return-path: Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id D106AF72 for ; Thu, 17 Nov 2016 17:01:44 +0100 (CET) Received: by mail-wm0-f48.google.com with SMTP id f82so155163380wmf.1 for ; Thu, 17 Nov 2016 08:01:44 -0800 (PST) In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E3925F412@shsmsx102.ccr.corp.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-11-17 03:51, Xu, Qian Q: > It is good that RC1 on Jan.11th is a hard deadline. We also need ensure that RC1 is a complete package with all features. If RC1 is out but missing some big features, then the test results on RC1 vs RC2 may have big difference. > So, could we ensure that RC1 is a complete feature package, if any feature missing RC1, then we may postpone the feature to 17.05? Does it make sense? Absolutely, yes. > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Tuesday, November 15, 2016 5:06 PM > To: Liu, Yong > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [dpdk-announce] DPDK 16.11 released > > Hi and thanks for sharing your time constraints, > > 2016-11-15 01:46, Liu, Yong: > > As prospect for 17.02, our intel validation team have some concern about the release date. > > The official day off for Chinese Sprint Festival holiday will be from 27th Jan to 3th Feb. > > Most of our members may ask for more days leave either before or after the official day off. > > From our previous experience, it will take 3~4 weeks to do the full function and performance test. > > If the first candidate release in the middle of Jan, we can do first > > round of validation and raise issues to developers. > > The integration deadline is January 5. > So we can target/expect a RC1 on January 11. > > > And after the holiday, we can keep on the validation process and finish in two weeks. > > If release date is after Feb, it will be hard for us to cover all cases in release window. > > Yes, we must remind that mid-January is a hard deadline for RC1. > Then the release will be in mid-February to make sure you have some time after the holidays. > What about Valentine's day? :)