From: Kevin Traynor <ktraynor@redhat.com>
To: "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Sitong Liu <siliu@redhat.com>,
Pei Zhang <pezhang@redhat.com>,
Raslan Darawsheh <rasland@mellanox.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Ian Stokes <ian.stokes@intel.com>,
Ali Alnubani <alialnu@mellanox.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Thomas Monjalon <thomas@monjalon.net>,
John McNamara <john.mcnamara@intel.com>,
Luca Boccassi <bluca@debian.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Akhil Goyal <akhil.goyal@nxp.com>
Subject: [dpdk-dev] DPDK 18.11.2 LTS update
Date: Thu, 16 May 2019 19:57:36 +0100 [thread overview]
Message-ID: <3085e8c3-ef1c-36f6-5c12-3c5e9b69e53c@redhat.com> (raw)
Hi All,
DPDK 18.11.2 will contain backports of relevant fixes from DPDK 19.05.
Plan is to have a 18.11.2 RC1 ready early next week for validation
teams. There are a small few outstanding backports that need authors
help - please send by next Monday so I can put into RC1.
Depending on what is found in validations, it is planned to release on
June 11th. Note, as things are more stable on dpdk-stable
(hopefully), not planning for further RCs unless they are needed.
I strongly recommend that anyone who is using or has an interest in DPDK
18.11 LTS plan to do some validation for your use cases on the RC.
Similar to 18.11.1 [1], I will add to the release notes what's been
fixed and a summary of reported validations so users are aware of this.
thanks,
Kevin.
[1]
http://doc.dpdk.org/guides-18.11/rel_notes/release_18_11.html#fixes-and-validation-in-18-11-stable-release
next reply other threads:[~2019-05-16 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 18:57 Kevin Traynor [this message]
2019-05-16 21:12 ` Thomas Monjalon
2019-05-16 23:23 ` Stephen Hemminger
2019-05-17 7:53 ` Kevin Traynor
2019-05-17 7:41 ` Kevin Traynor
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=3085e8c3-ef1c-36f6-5c12-3c5e9b69e53c@redhat.com \
--to=ktraynor@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@mellanox.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@mellanox.com \
--cc=siliu@redhat.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).