From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: DPDK Release Status Meeting 2022-09-15
Date: Thu, 15 Sep 2022 21:49:58 +0000 [thread overview]
Message-ID: <DM6PR11MB3227999652237F6FCC6EF568FC499@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]
Release status meeting minutes 2022-09-15
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD [No]
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 3 October 2022
* RC2: 23 October 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Ethdev reviews ongoing
* Some patches merged
* New drivers in this release
* Microsoft Azure Network Adatper (MANA) PMD
* There are several RDMA implementation now.
* Should we have RDMA bus driver?
* Google Virtual Ethernet (GVE)
* idpf (Infrastructure Data Path Function) PMD
* net/qdma PMD
* next-net-intel
* Patches waiting for pull
* next-net-mlx
* No update
* next-net-brcm
* No update
* next-net-mrvl
* Patches pushed and waiting for pull
* next-eventdev
* Patches pushed and waiting for pull
* next-virtio
* Issue in 22.11 branch causing deadlock in vHost
* next-crypto
* 30-35 patches merged and awaiting pull
* Review of crypto security and sessions rework patches
* Call for review comments from community because it
affects a lot of drivers
* Patches around BBDev
* ACC 100/200 patches
* FIPs validation patches need reviews acks
* Asym changes under review
* main
* Looking at EAL patches
* Windows Thread series has updates
* New arch type: LoongArch
* MLX5 new features coming around rte_flow
* CC Thomas for attention any patchsets that need early merge
LTS
---
Waiting for test results. LTS release on August 29th.
* 21.11.2
* 20.11.6
* 19.11.13
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialled for 19.11 to the 20.11 LTS cycle.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
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 9: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.
[-- Attachment #2: Type: text/html, Size: 14288 bytes --]
reply other threads:[~2022-09-15 21:50 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=DM6PR11MB3227999652237F6FCC6EF568FC499@DM6PR11MB3227.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=david.marchand@redhat.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).