DPDK announcements
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 17.02-rc1
Date: Thu, 19 Jan 2017 06:17:54 +0100	[thread overview]
Message-ID: <1911030.8L1mQGI9im@xps13> (raw)

A new DPDK release candidate is ready for testing:
	http://dpdk.org/browse/dpdk/tag/?id=v17.02-rc1

It is the first release candidate for DPDK 17.02.

There were a lot of things not ready until yesterday.
Fortunately things have been fixed in a rush for most of you.
Some features are still missing but could be integrated in RC2 if
there is no real impact on validation tests in progress.
This version must be released at mid-February, after China holidays.
We do not have so much time, so the focus will be on stabilization.

You can read the release notes in progress:
	http://dpdk.org/doc/guides/rel_notes/release_17_02.html
Some highlights:
	- new ethdev API for hardware filtering
	- new Solarflare networking driver
	- new ARM crypto driver
	- new Elastic Flow Distributor library
	- virtio-user/kernel-vhost as exception path

Please start now discussing the changes you plan to do for
the next release cycle (17.05).

Thank you everyone
and Happy New Year

                 reply	other threads:[~2017-01-19  5:17 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=1911030.8L1mQGI9im@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).