From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 17/06/2021
Date: Fri, 18 Jun 2021 16:03:22 +0000 [thread overview]
Message-ID: <SN6PR11MB30868B78FB352154F4B8E7A1FC0D9@SN6PR11MB3086.namprd11.prod.outlook.com> (raw)
Release status meeting minutes {Date}
=====================================
:Date: 17 June 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
.Participants:
* Arm
* Broadcom
* Canonical
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.08` dates
- Proposal/V1: Wednesday, 2 June (completed)
- -rc1: Monday, 5 July
- Release: Tuesday, 3 August
* Note: We need to hold to the early August release date since
several of the maintainers will be on holidays after that.
* `v21.11` dates (proposed and subject to discussion)
- Proposal/V1: Friday, 10 September
- -rc1: Friday, 15 October
- Release: Friday, 19 November
Subtrees
--------
* main
- Merged series from last release on PCI bus update for resets with VF devices
- Working on unit test failures from UNH lab
- Working on Solarflare patches
- Discussion ongoing about DMA Engine RFC
- Thomas applying some patchsets
** Series from Marvell - Raw device driver for basebase/PHY
** Auxiliary bus
** Mediated device - concerns from kernel on on similar DSA Driver:
*** https://lore.kernel.org/kvm/162164243591.261970.3439987543338120797.stgit@djiang5-desk3.ch.intel.com/
*** https://patchwork.kernel.org/project/kvm/cover/0-v1-324b2038f212+1041f1-vfio3a_jgg@nvidia.com/
* next-net
- Andrew working on testpmd patches for Windows - needs ack
- Bonding patches also need reviews
* next-crypto
- 4 new PMDs in this release
** CNXK - reviewed
** MLX - no update
** Intel QAT - will be reviewed next week
** NXP baseband - requires new version
* next-eventdev
- CNXK eventdev driver - awaiting further revisions
* next-virtio
- 4 series from Intel around the async data - under review
- 1 series from Maxime - kernel vdpa support - get mac address
from hardware. Under review and will send update
- Working on fixing issue in vhost with numa reallocation
* next-net-brcm
- Big patchset with 58 patches merged into dpdk-next-net-brcm sub tree.
- 4 to 5 patches pending on patchwork.
- Partially merged in main. The rest under review Thomas.
* next-net-intel
- Proceeding okay. No issues
* next-net-mlx
- Should be a small release for Mellanox
- Mainly fixes and RFCs
* next-net-mrvl
- CNXK ethernet driver (from last release).
- V4 should be merged next week.
LTS
---
* `v19.11` (next version is `v19.11.9`)
- RC3 tagged
- Target release date July 2
* `v20.11` (next version is `v20.11.2`)
- Tagged for release: RC1
* Distros
- v20.11 in Debian 11
- v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* None
.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 every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
*****
reply other threads:[~2021-06-18 16:03 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=SN6PR11MB30868B78FB352154F4B8E7A1FC0D9@SN6PR11MB3086.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).