From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 18.02-rc1
Date: Mon, 22 Jan 2018 03:02:34 +0100 [thread overview]
Message-ID: <11683762.3UVoxcIILy@xps> (raw)
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v18.02-rc1
Special attention was paid to not break the ABI in this release.
It means 18.02 could replace 17.11 without rebuilding the applications.
However it is advised to keep using 17.11 LTS for long term deployments.
The release notes are not complete yet:
http://dpdk.org/doc/guides/rel_notes/release_18_02.html
Some highlights:
- new license header (SPDX tag)
- bbdev (Wireless Base Band) device class
- ethdev probe notifications and port ownership
- Hyper-V platform driver
- AVF (Adaptive Virtual Function) ethdev driver
- IPsec offload in DPAA
- DPAA eventdev driver
- OPDL (Ordered Packet Distribution Library) eventdev driver
Some features may be integrated in 18.02-rc2:
- rawdev
- hotplug events API
- AMD drivers
- meson build system
Some planned features are postponed to 18.05:
- meter profile
- new devargs syntax
- multi-process channel
- dynamic memory management
- VF representor
- vhost-pci
- virtio-crypto
The planned release date for 18.02 is in two weeks.
We are very short in time. It will be probably a bit late,
but most changes must be done before the Chinese New Year holidays.
Please start testing and fixing bugs now.
When finding a new bug, please report it on bugzilla:
http://dpdk.org/tracker/
Thank you everyone
reply other threads:[~2018-01-22 2:03 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=11683762.3UVoxcIILy@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).