DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 18.05-rc4
Date: Tue, 15 May 2018 22:49:25 +0200	[thread overview]
Message-ID: <17754390.2HoNqvqDxk@xps> (raw)

A new DPDK release candidate is ready for testing:
	https://dpdk.org/browse/dpdk/tag/?id=v18.05-rc4

This small release candidate is published one day after -rc3.
The reason is fixing two outstanding bugs introduced in recent commits:
	- PCI probing broken for device string >8B
	- option --file-prefix broken

The plan is not changed since yesterday:
We can target to make -rc5, -rc6 and finally release on 25th of May.
As usual, please test this release candidate as much as you can,
and check for possible behaviour or performance regressions.

Thank you everyone

                 reply	other threads:[~2018-05-15 20:49 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=17754390.2HoNqvqDxk@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).