From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 26/03/2020
Date: Tue, 31 Mar 2020 09:55:14 +0000 [thread overview]
Message-ID: <MWHPR1101MB21588DCE927B93413003F9CDFCC80@MWHPR1101MB2158.namprd11.prod.outlook.com> (raw)
Minutes 26 March 2020
---------------------
Agenda:
* Release Dates
* Subtrees
* OvS
Participants:
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
* ARM
Release Dates
-------------
* v20.05 dates:
* Proposal/V1: Wednesday 18 March 2020
* Integration/Merge/RC1: Friday 17 April 2020
* Release: Wednesday 20 May 2020
* Marvell, Arm, Mellanox & Broadcom already sent roadmap for 20.05, all
vendors please share the roadmap for the release.
Subtrees
--------
* main
* Some patches merged around EAL.
* Added Travis CI support for ARM.
* Still some random failures. Under investigation.
* There are several last series that need reviews in this release.
* This is challenging.
* We need the whole community involved with reviewing.
* Three big patch sets from Marvell
* IF proxy, Trace and Graph.
* Call for review of the testing guidelines:
* http://mails.dpdk.org/archives/web/2020-March/001346.html
Fixed issues with
* next-net
* Andrew Rybchenko took over maintenance this week from Ferruh.
* next-crypto
* Some patches merged
* Half of the backlog reviewed
* No major issues at the moment
* next-eventdev
* Some patches (10-15) to be merged.
* next-virtio
* Reviewing vHost IO IOAT Support Series
* Some progress in the discussion on the list.
* Agreed to do it in the vHost library.
* next-net-intel
* No update.
* next-net-mlx
* Working on a couple of patch series.
* LTS
* 18.11.7
* -rc1 is out.
* Release planned for 14 April
* 19.11.1 released
* https://mails.dpdk.org/archives/dev/2020-March/160132.html
OvS
---
* Second OVS-DPDK meeting done, thanks Kevin for notes and recording:
* https://bluejeans.com/s/6wR3z
* Intel is preparing something to present in next meeting
* Planning to do more test on 19.11.1
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.
reply other threads:[~2020-03-31 9:55 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=MWHPR1101MB21588DCE927B93413003F9CDFCC80@MWHPR1101MB2158.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).