From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Xu, Qian Q" <qian.q.xu@intel.com>
Cc: "Liu, Yong" <yong.liu@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-announce] DPDK 16.11 released
Date: Thu, 17 Nov 2016 17:01:43 +0100 [thread overview]
Message-ID: <2542149.maapeWSFuo@xps13> (raw)
In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E3925F412@shsmsx102.ccr.corp.intel.com>
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 <yong.liu@intel.com>
> 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? :)
prev parent reply other threads:[~2016-11-17 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 22:22 Thomas Monjalon
2016-11-15 1:46 ` Liu, Yong
2016-11-15 9:05 ` Thomas Monjalon
2016-11-17 3:51 ` Xu, Qian Q
2016-11-17 16:01 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2542149.maapeWSFuo@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=qian.q.xu@intel.com \
--cc=yong.liu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).