From: "Mcnamara, John" <john.mcnamara@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: "Stokes, Ian" <ian.stokes@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>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 23/5/2019
Date: Thu, 23 May 2019 11:46:46 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F642A3F@IRSMSX103.ger.corp.intel.com> (raw)
Minutes 23 May 2019
-------------------
Agenda:
* Release Dates
* Subtrees
* LTS
* OvS
* Opens
Participants:
* ARM
* Broadcom
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* RedHat
Release Dates
-------------
* v19.08 dates:
* Proposal/V1 Monday 03 June 2019
* Integration/Merge/RC1 Monday 01 July 2019
* Release Thurs 01 August 2019
* Schedule updated on roadmap page:
https://core.dpdk.org/roadmap/
* Reminder to send roadmaps for the release, it helps planning
* Intel is planning to send roadmap by the end of this week
* Marvell will have new PMDs and will provide a roadmap
* v19.11 proposed dates, *please comment*,
* Proposal/V1 Friday 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
* Constraints:
* PRC holidays on October 1-7 inclusive, rc1 shouldn't overlap with it
* US DPDK Summit on mid-November, better to have release before summit
Subtrees
--------
* Main
* No activity this week.
* Will target weekly merge starting next week.
* Next-Net
* RTE_prefix patch to be merged early.
* This will cause a lot of breakage in patches/backports.
* There is a script to convert the prefix automatically.
* Next-virtio
* Not many patches yet.
* Patch for SPDK.
* Under review. There is a new API(s).
* Requested some example code to demonstrate the APIs.
* Next-Crypto
* No patches yet.
* Next-Eventdev
* New timer patch for eventdev. Needs to be reviewed.
* Next-Ip-pipeline
* No update
* Stable trees
* 17.11.6
* 17.11.6 released 22 May 2019
* Testing with Red Hat lab (was down temporarily).
* 18.11.2
* 18.11.2-RC1 released 21 May 2019
* 11 June is the planned release date.
* Will be looking for testing from the community.
OvS
---
* 18.11.2 RC1 is out.
* Need to look at the impact of the rte_prefix.
* Will rebase end-of-month DPDKmaster to OvS
* 2.12 release dates
* 1 July for feature freeze
* No features beyond that date
* 20th July for code freeze
Conferences
-----------
* DPDK Userspace summit: DPDK Userspace · Sept. 19-20, 2019
https://www.dpdk.org/event/dpdk-userspace-bordeaux/
* CFP Opens: Monday, April 29
* CFP Closes: Friday, May 24
* Reminder of the short CFP duration and deadline is approaching
* US summit dates are not fixed yet
Opens
-----
* Akhil can able to spend more time on crypto sub-tree and there is a potential
co-maintainer from Arm, can close this open for now
* There still some Coverity defects open, some of them are from Marvell, NXP
drivers, it would be great to close them
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
next reply other threads:[~2019-05-23 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 11:46 Mcnamara, John [this message]
2019-05-23 13:55 ` David Marchand
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=B27915DBBA3421428155699D51E4CFE23F642A3F@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ian.stokes@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).