From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-announce <announce@dpdk.org>
Subject: [dpdk-announce] release candidate 18.05-rc3
Date: Tue, 15 May 2018 00:18:36 +0100 [thread overview]
Message-ID: <6d3ec1fa-581d-a50e-268b-ad0605f0e65c@intel.com> (raw)
In-Reply-To: <2233576.Okp3jBAIYA@xps>
A new DPDK release candidate is ready for testing:
https://dpdk.org/browse/dpdk/tag/?id=v18.05-rc3
The release notes should be complete now:
http://dpdk.org/doc/guides/rel_notes/release_18_05.html
What's new in -rc3?
- proper runtime directory
- consistent checks in offload API
- compressdev API
- Intel compressdev software driver
- eventdev crypto adapter
- NXP devices blacklisting
- DPAA2 QDMA raw driver
- DPAA2 Command Interface raw driver
- Intel FPGA bus
- BPF
Some planned features are postponed to 18.08:
- Hyper-V bus and NetVSC driver
- TAP TSO
- testpmd simulation of noisy host
It is a big release candidate (322 patches),
but next one is expected to include only some bug fixes,
tooling or documentation updates.
Everybody is tired by this release which lasts too long.
So let's try to minimize new risks in order to close it soon.
We can target to make -rc4, -rc5 and finally release on 25th of May.
As usual, please test this release candidate as much as you can,
and check for possible behaviour or performance regressions.
There are some open bugs to check in bugzilla:
https://dpdk.org/tracker/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&product=DPDK
Thank you everyone
parent reply other threads:[~2018-05-14 23:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2233576.Okp3jBAIYA@xps>]
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=6d3ec1fa-581d-a50e-268b-ad0605f0e65c@intel.com \
--to=ferruh.yigit@intel.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).