From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 11/06/2020
Date: Wed, 17 Jun 2020 15:34:25 +0000 [thread overview]
Message-ID: <SN6PR11MB30866787CE8748709F667828FC9A0@SN6PR11MB3086.namprd11.prod.outlook.com> (raw)
Minutes 11 June 2020
--------------------
Agenda:
* Meeting
* Release Dates
* Subtrees
* OvS
Participants:
* Arm
* Debian/Microsoft
* Intel
* Mellanox
* Red Hat
Meeting
-------
* Call for maintainers to follow up on patches that have stalled.
* There are several patchset hanging around but not progressing.
* Maintainers should ask people for reviews or to respond to open comments.
* This would help overall progress with merging.
* From next week (18 June) we with use Jitsi instead of Skype for meetings:
* https://meet.jit.si/DPDK
Release Dates
-------------
* v20.08 dates:
* Proposal/V1: Friday, 12 June 2020
* -rc1: Wednesday, 8 July 2020
* -rc2: Monday, 20 July 2020
* Release: Tuesday, 4 August 2020
Subtrees
--------
* main
* Series from Stephen Hemminger on changing whitelist/blacklist:
* http://mails.dpdk.org/archives/dev/2020-June/170240.html
* There are a lot of patch series in this release including:
* RCU integration
* Bitops - ready for merge
* Lcore hotplug - for attaching external threads
* Vfio VF token interface
* IF Proxy
* Several Windows series
* next-net
* Merging on track ahead of V1 deadline.
* next-crypto
* No update this week.
* next-eventdev
* No update this week.
* next-virtio
* Not a lot of patches.
* Changes and improvements in virtio/vhost initialization.
* Significant rework of the vDPA API - goal is to remove the experimental tag.
* next-net-mlx
* Some big series ready to be merged or pending - patches to support Windows.
LTS
---
* v19.11.3-rc1 is out, please test
* https://mails.dpdk.org/archives/dev/2020-June/169263.html
* Test results from Intel and Mellanox.
* Waiting for results from Microsoft, OvS and Red Hat.
* v18.11.9 in progress
* Majority of patches backported.
* Issues with GCC10.
* RC1 towards the end of next week.
* Then moving to validation phase.
OvS
---
* Validating CVE fixes
* A performance drop observed previously couldn't be replicated.
* Release feature deadline is beginning of the July and code freeze mid July
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-06-17 15:34 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=SN6PR11MB30866787CE8748709F667828FC9A0@SN6PR11MB3086.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=dev@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).