From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 19.11-rc3
Date: Thu, 21 Nov 2019 01:19:17 +0100 [thread overview]
Message-ID: <2114047.gUUQFilDeZ@xps> (raw)
A new DPDK release candidate is ready for testing:
https://git.dpdk.org/dpdk/tag/?id=v19.11-rc3
142 patches were integrated.
The release notes so far:
http://doc.dpdk.org/guides/rel_notes/release_19_11.html
It should be completed with a list of tested hardware.
Highlights of 19.11-rc3:
- new ABI versioning
- KNI with VA
The -rc4 should include only some bug fixes, doc and tooling.
This next milestone is expected to be released on Tuesday 26th.
There are some open bugs to check in bugzilla:
https://bugs.dpdk.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&product=DPDK
Please hurry up to do the last checks and bug fixes,
in order to have DPDK 19.11 out during the next week.
You may share some release validation results
by replying to this message (at dev@dpdk.org).
If you are preparing the next release cycle, please send your v1 patches
before the 20.02 proposal deadline, which will happen on December 6th.
It is also time to build an estimated roadmap for the next cycles.
Thank you everyone
reply other threads:[~2019-11-21 0:19 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=2114047.gUUQFilDeZ@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).