From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=JUBqPJrk3Macg6621CUgE8XvIp5UeqKauG2LbSxY7JM=; b=Qfg7b057TDpbpDqAwwjXFjSSfS34tZTVAaAoghaINi3Bzv4X1WRCE4NG9PGHQa5D+9 qbzQ0g0X7NnGoXm2DUsVKaFZMZ1czkvgEbHPdj5G0LkPiYSH9tgtgLfaafACwDkSptxM j/piSaQBMWYdKlv5SQT04EJlNR7QX5y7+0Uh7/iorjzYTn50xZyBsk9F2qPbnkGmVxil aVbvLi0GjwD3NG26nZe1KyJVAuppdp6K3uS3nHquk8So0AuNpwZJkOBNu+Nhqke29KPB XIFPtdyrn55FruXDhjaR7hWUlkdRrg9gBVftVSzY42vo/cB+o21BX4lW+L3w2ZU/0xeK Z8vw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=JUBqPJrk3Macg6621CUgE8XvIp5UeqKauG2LbSxY7JM=; b=luUlovUnXj0OuZG7GFD7fCM85qIg48LPPODCEjRvwJrPoIiVujFOWo+hO9+WMsUXy8 LodJaZGQ4UbGHhs8RN2OEzdK2PA5sowaWplhmGuEv2HsHwC37VE5NDPybcm+G+cPsCmq NJ+oFIGNdDmrGPxlX/1ZsvpqH3OTeikBU1UYWQ5NjCSlR3lq9WGtURYKTojIdkLbauiw piAG91wu3JTROROykXEZ2LgX1hcOyWLSS2Pdz7s97SzSpnv+xemvkuKFWoBcRvoL8DtC tDnkIYwZgkj4hYYYWnocS17bZCL5efh//bwdvRwgHhwEKwuIXr6H3aeodxK8pAMbLGBK i6ig== X-Gm-Message-State: ABUngvfYTs1UMlJfZU+8ZL4lkoj97cuet4IFW7NpEeVR8g9MJEmBThkqT0IWVZCPfKQeU2xL X-Received: by 10.28.214.133 with SMTP id n127mr18701094wmg.28.1479398504530; Thu, 17 Nov 2016 08:01:44 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id 81sm4482902wmw.7.2016.11.17.08.01.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Nov 2016 08:01:43 -0800 (PST) From: Thomas Monjalon To: "Xu, Qian Q" Cc: "Liu, Yong" , dev@dpdk.org Date: Thu, 17 Nov 2016 17:01:43 +0100 Message-ID: <2542149.maapeWSFuo@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E3925F412@shsmsx102.ccr.corp.intel.com> References: <3980631.9YyyMl1DK9@xps13> <1609004.OL7hRRQnMz@xps13> <82F45D86ADE5454A95A89742C8D1410E3925F412@shsmsx102.ccr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-announce] DPDK 16.11 released 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: Thu, 17 Nov 2016 16:01:45 -0000 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? :)