From: "St Leger, Jim" <jim.st.leger@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"announce@dpdk.org" <announce@dpdk.org>
Subject: Re: [dpdk-announce] [dpdk-dev] release candidate 2.2.0-rc3
Date: Tue, 8 Dec 2015 04:55:16 +0000 [thread overview]
Message-ID: <00B2C372B6E6DA4FB04934511BF0564A3EFBE1F6@FMSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <4025702.psNOgjEjHI@xps13>
Thomas:
Thanks for all the incredibly hard work over the past week or so (and so much time on the weekend!) Great job getting this RC out. On to RC4 and hopefully us closing in on the full R2.2 release.
Thank you and the rest of the community.
Jim
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
Sent: Monday, December 7, 2015 7:32 PM
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 2.2.0-rc3
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v2.2.0-rc3
Changelog (main changes since 2.2.0-rc2)
- enhancements:
* new Netronome nfp networking driver
* pipeline example
* new ethtool example
* tools & dev scripts
* standard make install
- fixes for:
* compilation
* ARM
* drivers
* examples
* unit tests
The release 2.2.0 may be closed at the end of this week if no major bug is seen and if compilation is validated in the main environments.
So only important fixes and documentation updates are accepted.
There will be a fourth (and probably last) release candidate.
Thank you everyone
prev parent reply other threads:[~2015-12-08 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 2:31 [dpdk-announce] " Thomas Monjalon
2015-12-08 4:55 ` St Leger, Jim [this message]
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=00B2C372B6E6DA4FB04934511BF0564A3EFBE1F6@FMSMSX114.amr.corp.intel.com \
--to=jim.st.leger@intel.com \
--cc=announce@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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).