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 Release Status Meeting 2021-11-18
Date: Fri, 19 Nov 2021 16:41:24 +0000 [thread overview]
Message-ID: <DM6PR11MB322745D788281D2F7C2A4057FC9C9@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2184 bytes --]
Release status meeting minutes 2021-11-18
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates: http://core.dpdk.org/roadmap/#dates
* Doc, tool, and minor fixes (-rc4): 24November 2021
* Release: 26 November 2021
* There is also a proposal to have only 3 releases in 2022:
* 22.03, 22.07, 22.11
* Dates will be finalized after 21.11 release
Subtrees
--------
* next-net
* Fixed merged in RC3
* Mainly doc patches in RC4
* next-net-intel
* Mainly doc patches in RC4
* next-net-mlx
* A few remaining fixes to be merged
* Majority merged in RC3
* next-net-brcm
* No update.
* next-net-mrvl
* No patches.
* next-eventdev
* Doc series only (v4)
* next-virtio
* 3 patches for vhost async (postponed to next release)
* next-crypto
* A few BXP patches/fixes to be merged
* main
* RC3 released
* Only doc, tools and fixes will be merged in RC4
* Wed 24 for RC4 and release on Friday 26
* Subtree maintainers should rebase to main to pick up Fedora 35 fixes
* Please submit 22.02/22.03 roadmaps next week.
LTS
---
* There is a proposal to make 19.11 LTS into a 3 year release
* 20.11.3 released on Monday Sept 6
* 19.11.10 released on Monday Sept 6
* 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 Thursday 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<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 16571 bytes --]
reply other threads:[~2021-11-19 16:41 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=DM6PR11MB322745D788281D2F7C2A4057FC9C9@DM6PR11MB3227.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).