From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] delay for 17.02-rc1
Date: Mon, 16 Jan 2017 17:02:53 +0100 [thread overview]
Message-ID: <4833533.9kVdhXKYOk@xps13> (raw)
Hi all,
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 the mainline, are ready.
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
Which solutions do we have?
1/ close 17.02 features now and frustrate everyone
2/ postpone some patches to RC2 if they do not disturb validation too much
3/ hurry up
Comments are welcome
next reply other threads:[~2017-01-16 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 16:02 Thomas Monjalon [this message]
2017-01-17 8:37 ` Xu, Qian Q
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=4833533.9kVdhXKYOk@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
/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).