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 01/07/2021
Date: Thu, 1 Jul 2021 16:30:18 +0000 [thread overview]
Message-ID: <BYAPR11MB30787E4D2F26D4EA854EDE51FC009@BYAPR11MB3078.namprd11.prod.outlook.com> (raw)
Release status meeting minutes {Date}
=====================================
:Date: 1 July 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
.Participants:
* Broadcom
* Canonical
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.08` dates
- Proposal/V1: Wednesday, 2 June (completed)
- -rc1: Wednesday, 7 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
- Backlog is a little big at the moment. RC1 will probably slip to Wednesday 7th July.
- Most subtrees PRs are ready or close to ready.
- Still waiting update on Solarflare patches.
- New auxiliary bus patch series should go into this release.
* next-net
- Testpmd patchset for Windows.
- Looking at net/sfc patches.
* next-crypto
- 4 new PMDs in this release:
** CNXK - reviewed - awaiting final version for RC1.
** MLX - still in progress. New version will be sent today.
** Intel QAT - under review.
** NXP baseband - requires new version.
* next-eventdev
- PR for RC1 will be completed today.
* next-virtio
- PR posted yesterday.
* next-net-brcm
- All patches in sub-tree waiting to be pulled.
* next-net-intel
- Proceeding okay. No issues
* next-net-mlx
- PR not pulled due to comments that need to be addressed.
- New version sent today.
* next-net-mrvl
- Pull request for RC1 sent.
LTS
---
* `v19.11` (next version is `v19.11.9`)
- RC3 tagged.
- Target release date July 2, however there are some late reported
MLX regressions that are under investigation.
- There are 2 other known issues:
** Plenty of GCC11 and Clang build issues were fixed, but 19.11.9
is not yet compatible with clang 12.0.0. Fixes are discussed
and a potential 3 backports identified for 19.11.10:
https://bugs.dpdk.org/show_bug.cgi?id=733
** Due to a kernel patch backport in SUSE Linux Enterprise Server 15
SP3 6, compilation of kni fails there:
https://bugs.dpdk.org/show_bug.cgi?id=728
* `v20.11` (next version is `v20.11.2`)
- RC2 released
- Some test reports coming in (Intel, MLX)
- 6 July is proposed release date.
* 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
-----
* There in an ongoing initiative around ABI stability which was
discussed in the Tech Board call. A workgroup has come up
with a list of critical and major changes required to let us
extend the ABI without as much disruption. For example:
** export driver interfaces as internal
** hide more structs (may require uninlining)
** split big structs + new feature-specific functions Major
** remove enum maximums
** reserved space initialized to 0
** reserved flags cleared
* We need to fill details and volunteers in this table:
https://docs.google.com/spreadsheets/d/1betlC000ua5SsSiJIcC54mCCCJnW6voH5Dqv9UxeyfE/edit?usp=sharing
* The DPDK North America Summit will be on July 12-13. Registration is free.
https://events.linuxfoundation.org/dpdk-summit-north-america/
.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-07-01 16:30 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=BYAPR11MB30787E4D2F26D4EA854EDE51FC009@BYAPR11MB3078.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).