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-06-30
Date: Thu, 30 Jun 2022 10:47:42 +0000 [thread overview]
Message-ID: <DM6PR11MB322783612A4AB40985424609FCBA9@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3219 bytes --]
Release status meeting minutes 2022-06-30
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.07:
* V1 deadline: 10 April 2022
* RC1: 8 June 2022
* RC2: 23 June 2022
* RC3: 4 July 2022 - was 30 June 2022
* RC4: 8 July 2022
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* V1 deadline: 14 August 2022
* RC1: 3 October 2022
* RC2: 23 June 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* RC2 released
* Prepping for RC3
* Patch for MTU in PCAP Driver - needs reviews
* next-net-intel
* Get update
4 patches waiting for upstream
* Looking at fix for GCC12 issue in ice driver
* next-net-mlx
* 2 small patches for private testpmd
* next-net-brcm
* No update
* next-net-mrvl
* Mainly complete after RC2
* next-eventdev
* Some fixes from Intel
* next-virtio
* Some reviews to do
* Prepping a PR for RC3 around docs and fixes
* next-crypto
* Most patches merged in RC2
* Looking at docs and fixes
* main
* Merged last fixes for GCC 12
* Still some issues with cross compilation
* Merged NULL pointer/checks patches
* Series for memory leaks needs some rework
* Sent first RFC on rte_bus
* Please send **and** review deprecation notices:
https://patchwork.dpdk.org/project/dpdk/list/?series=&q=deprecat
Other
-----
* DPDK Summit: https://events.linuxfoundation.org/dpdk-userspace-summit/
* Call for papers: https://linuxfoundation.smapply.io/prog/dpdk_userspace_summit_2022/
Dates to Remember:
CFP Opens: Monday, June 27 at 12:00 am PDT
CFP Closes: Friday, July 22 at 11:59 PM PDT
Speaker Notifications: August 1
Schedule Announcement: Week of August 1
Presentation Slide Due Date: Tuesday, August 30
Event Dates: Tuesday, September 6 - Thursday, September 8, 2022
LTS
---
* 21.11.2
* Back porting in progress
* 21.11.1 released April 26th
* 20.11.6
* Backporting waiting for RC2
* 20.11.5 released April 4th
* 19.11.13
* Backporting waiting for RC2
* 19.11.12 released April 7th
* 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" for the invite.
[-- Attachment #2: Type: text/html, Size: 17126 bytes --]
next reply other threads:[~2022-06-30 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 10:47 Mcnamara, John [this message]
2022-06-30 11:01 ` David Marchand
2022-06-30 11:43 ` Ferruh Yigit
2022-06-30 11:57 ` David Marchand
2022-06-30 12:40 ` Ferruh Yigit
2022-06-30 12:43 ` Dodji Seketeli
2022-06-30 17:52 ` Ferruh Yigit
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=DM6PR11MB322783612A4AB40985424609FCBA9@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).