From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 19.11-rc1
Date: Mon, 28 Oct 2019 00:34:17 +0100 [thread overview]
Message-ID: <1779345.uagyu2ZT7m@xps> (raw)
A new DPDK release candidate is ready for testing:
https://git.dpdk.org/dpdk/tag/?id=v19.11-rc1
There are 1045 patches accumulated in the master branch
since the last release. It is more than enough to have a new tag.
Note that this -rc1 is exceptionnally not feature-complete.
We are expecting more major features in the upcoming -rc2 (in 2 weeks).
The release notes so far:
http://doc.dpdk.org/guides/rel_notes/release_19_11.html
Please think about updating the release notes when you add a feature.
Highlights of 19.11-rc1, grouped by category:
General:
- prepare for 1 year without ABI breakage
- dynamic mbuf
- eBPF arm64 JIT
Networking:
- Hisilicon hns3 driver
- NXP PFE driver
- virtio packed ring optimizations
Cryptography:
- session-less asymmetric crypto
- Marvell Nitrox driver
- Marvell OCTEON TX2 crypto driver
- IPsec SAD API
Applications:
- IOAT example
- several examples are removed
We will close this release cycle before the end of November.
DPDK 19.11-rc2 is expected on 8th of November.
Thank you everyone
reply other threads:[~2019-10-27 23:34 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=1779345.uagyu2ZT7m@xps \
--to=thomas@monjalon.net \
--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).