From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 16.11-rc1
Date: Fri, 14 Oct 2016 03:08:47 +0200 [thread overview]
Message-ID: <3592985.xEdqf9UpuT@xps13> (raw)
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v16.11-rc1
It is the first release candidate for DPDK 16.11.
It happens a bit late, though there are still some features missing.
This version must be released before mid-November.
Therefore we have 3 weeks to make the validation, fixes and decide
which remaining features can enter without hurting the validation process.
The easy decision would be to stop accepting large patches and new features.
The release notes shall be completed:
http://dpdk.org/browse/dpdk/tree/doc/guides/rel_notes/release_16_11.rst
Some highlights:
- EAL device object rework
- more offloads
- improved vhost
- virtio for NEON
- new crypto libraries
- usual updates of drivers
- ivshmem library removal
Please start now discussing the changes you plan to do for
the next release cycle (17.02).
Thank you everyone
reply other threads:[~2016-10-14 1:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3592985.xEdqf9UpuT@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=announce@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).