From: "Liu, Yong" <yong.liu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] DPDK 16.11 released
Date: Tue, 15 Nov 2016 01:46:57 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E6032660B@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <3980631.9YyyMl1DK9@xps13>
Thomas, it's great to hear that DPDK16.11 released just in time.
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.
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.
Thanks,
DPDK STV team
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, November 14, 2016 6:23 AM
> To: announce@dpdk.org
> Subject: [dpdk-dev] [dpdk-announce] DPDK 16.11 released
>
> The new features for the 17.02 cycle must be submitted before December 4.
> There is a long list of expected works:
> http://dpdk.org/dev/roadmap
> It means we will have a huge workload to properly review all the new stuff
> before the end of the year. Do not forget to help reviewing patches from
> others if we want to have a chance to integrate everything in time.
>
>
> Thanks everyone
next prev parent reply other threads:[~2016-11-15 1:47 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 [this message]
2016-11-15 9:05 ` Thomas Monjalon
2016-11-17 3:51 ` Xu, Qian Q
2016-11-17 16:01 ` Thomas Monjalon
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=86228AFD5BCD8E4EBFD2B90117B5E81E6032660B@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).