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 2022-01-20
Date: Thu, 20 Jan 2022 13:03:11 +0000 [thread overview]
Message-ID: <DM6PR11MB322724E83362A3AF9A86C1BFFC5A9@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2935 bytes --]
Release status meeting minutes 2022-01-20
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed dates for 22.03:
* 22.03 V1 2021-12-31
* 22.03 Merge 2022-02-11
* 22.03 Release 2022-03-11
See also http://core.dpdk.org/roadmap/#dates
And some provisional dates for the subsequent releases:
* 22.07 V1 2022-05-06
* 22.07 Merge 2022-06-10
* 22.07 Release 2022-07-15
* 22.11 V1 2022-09-09
* 22.11 Merge 2022-10-18
* 22.11 Release 2022-11-18
Subtrees
--------
* next-net
* Reviewing and merging has started
* PR will be created EOD 2022-01-21
* Some Ethdev patches under review
- Patchset for rte_flow bulk insertion to review
- Currently no hardware backend
* New driver: Net/SPNIC from @ramaxel.com
* next-net-intel
* Some patches merged to next-net
* next-net-mlx
- Some patches merged and pulled
- Will submit some other patches that are awaiting changes
* next-net-brcm
* Some patchsets merged
* Some more fixes in the pipeline, but nothing major right now
* next-net-mrvl
- Some patches being pushed
- Expecting around 30 patches
* next-eventdev
* 5 patches from Intel
* 15 patches from Marvell
* All under review
* next-virtio
* Some reviewing ongoing
* Reviewing patch on vhost async
* Adding stats to vhost library (probably in 22.07)
* next-crypto
* Not many merges yet
* Starting to review and merge
* main
* Some series for Windows
- Unit tests - awaiting new version
- Threading API - needs reviews
* Patches for Mempool, Ring and EAL
* EAL series from Dmitri under review
* Automated delegation in patchwork
* There is a need for some new maintainers since some have stepped down
* TAP and Bonding in particular
LTS
---
* 21.11.1
* Target April (after 22.03)
* 20.11.4
* Released on 2022-01-17
* 19.11.11
* Released on 2022-01-07
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
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 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<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 21142 bytes --]
reply other threads:[~2022-01-20 13: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=DM6PR11MB322724E83362A3AF9A86C1BFFC5A9@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).