From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 16.07-rc1
Date: Mon, 04 Jul 2016 03:59:44 +0200 [thread overview]
Message-ID: <2201334.fHQMH7fcQu@xps13> (raw)
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v16.07-rc1
It is the first release candidate for DPDK 16.07.
This version must be released before the end of July.
Therefore we have 3 weeks to make the validation and fixes.
The current release notes show most of the main changes:
http://dpdk.org/browse/dpdk/tree/doc/guides/rel_notes/release_16_07.rst
There were a lot of changes in mempool, thus it is important to
check the memory usage and the performances.
The last big changes which could be accepted in the RC2 are:
- pmdinfo
- rte_pci_dev_ids.h removal
- possible more EAL cleanup
If you are not involved in the last minute changes, you can help by
- testing and reporting bugs
- reviewing pending patches
- reviewing and testing at the same time :)
Please start now discussing the changes you plan to do for
the next release cycle (16.11).
Thank you everyone
reply other threads:[~2016-07-04 1:59 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=2201334.fHQMH7fcQu@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).