From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 17.05-rc4
Date: Mon, 08 May 2017 01:43:07 +0200 [thread overview]
Message-ID: <2599272.pe6CB3uP40@xps> (raw)
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v17.05-rc4
If there is no major bug discovered, there will be no RC5.
>From now on, each patch accepted in 17.05 is considered as an exception.
If you think your patch is exceptional, please insist.
It is time to think at the next release (17.08).
You are welcome to contribute to the roadmap.
After a look at the deprecation notices (which need 3 acknowledgements),
you could also start reviewing the next features:
http://dpdk.org/dev/patchwork/project/dpdk/list/?state=10&archive=
Thank you
reply other threads:[~2017-05-07 23:43 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=2599272.pe6CB3uP40@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).