From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"Akhil Goyal" <akhil.goyal@nxp.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
"Yongseok Koh" <yskoh@mellanox.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"O'Hare, Cathal" <cathal.ohare@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 24/01/2018
Date: Fri, 25 Jan 2019 09:24:33 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F512773@IRSMSX103.ger.corp.intel.com> (raw)
Release Status Meeting 24/01/2018
28 June 2018
09:32
Agenda
------
* Subtrees
* Bugzilla
* Dates
Subtrees
--------
* Next-Net
* There are no critical/blocking issues. There is only a bunch of
patches merged, again nothing critical. Pulled from sub-trees.
It can be ready for Friday for rc4.
* Next-Crypto
* No patches
* Next-virtio
* Have prepared branch with 4 patches.
* Next-Eventdev
* No patches
* Next-Ip-pipeline
* No patches
* Master
* Documentation patches
RC4 target for Friday 25 January.
RC3 Testing
-----------
* No critical or very big issues for RC3 - from Intel Testing
LTS Testing
-----------
* Intel cannot test the LTS until after Chinese Spring Festival
* Should be able to start retesting in the week of Feb 18th
* Questions from Intel Test about the use of the Stable Tree.
Do people use it? Each stable/LTS release requires a lot of
testing and there are currently 3 releases to be tested.
Deprecation notices
-------------------
Please review the deprecation notices below:
* doc: add deprecation notice for meson: http://patches.dpdk.org/patch/49877/
* doc: add deprecation notice to remove rte meter color: http://patches.dpdk.org/patch/48712/
* doc: update API deprecation for device reset: http://patches.dpdk.org/patch/44990/
* doc: announce change of rte service API parameter type: http://patches.dpdk.org/patch/49987/
* doc: announce ring API change: http://patches.dpdk.org/patch/49961/
OVS 2.11 Status
---------------
* 2.11 branched from master January 18th.
* 4 week stabilization period.
* Release targeted February 18th~.
DPDK 19.05
----------
* Request for to try get some changes in early
* Agreement to accept proposed dates for 19.05
* Intel to submit patch to website to update dates
* Proposal Deadline: Friday 1 March 2019
* Merge deadline: Friday 22 March 2019
* RC1 release: Friday 29 March 2019
* Release: Friday 10 May 2019
next reply other threads:[~2019-01-25 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 9:24 Mcnamara, John [this message]
2019-01-25 13:42 ` Jay Rolette
2019-01-25 16:40 ` Thomas Monjalon
2019-01-25 16:53 ` Jay Rolette
2019-01-25 17:05 ` Thomas Monjalon
2019-01-25 21:16 ` Aaron Conole
2019-01-25 23:37 ` Ferruh Yigit
2019-01-26 1:01 ` Thomas Monjalon
2019-01-28 14:27 ` Aaron Conole
2019-02-01 16:57 ` Mcnamara, John
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=B27915DBBA3421428155699D51E4CFE23F512773@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=cathal.ohare@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=maxime.coquelin@redhat.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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).