From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 19.02-rc3
Date: Sun, 20 Jan 2019 23:25:40 +0100 [thread overview]
Message-ID: <4706291.AoiGW22Clv@xps> (raw)
A new DPDK release candidate is ready for testing:
https://git.dpdk.org/dpdk/tag/?id=v19.02-rc3
The release notes are almost complete:
http://doc.dpdk.org/guides/rel_notes/release_19_02.html
There are some open bugs to check in bugzilla:
https://dpdk.org/tracker/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&product=DPDK
Please hurry up to do the last checks and bug fixes this week,
in order to have DPDK 19.02 out in two weeks.
You may share some release validation results
by replying to this message (at dev@dpdk.org).
In order to prepare the next cycle, the deprecation notices
must be reviewed, and the roadmap topics proposed on the mailing list.
Some deadline dates are proposed in the release status meeting:
http://mails.dpdk.org/archives/dev/2019-January/123625.html
Feel free to approve or comment in the thread above.
Thank you everyone
PS: Registration for India summit is open:
http://www.cvent.com/d/g6q7jz/4W
reply other threads:[~2019-01-20 22:25 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=4706291.AoiGW22Clv@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).