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 2023-09-07
Date: Thu, 7 Sep 2023 10:43:18 +0000 [thread overview]
Message-ID: <PH8PR11MB6804CE4270DAB0259E3B572FFCEEA@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3094 bytes --]
Release status meeting minutes 2023-09-07
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 23.11:
* V1: 12 August 2023
* RC1: 29 September 2023
* RC2: 20 October 2023
* RC3: 27 October 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* New driver from Napatech
* New driver RNP: https://patchwork.dpdk.org/project/dpdk/list/?series=29118
* 1 other new driver
* More reviews are required.
* next-net-intel
* 12 patches awaiting merge.
* next-net-mlx
* Some patches coming next week.
* next-net-mvl
* All patches merged.
* next-eventdev
* Intel patches merged
* 12 patches pending.
* next-baseband
* 2 series under review.
* next-virtio
* Working on improvements for VDUSE.
* Other patches under review.
* No big features for now.
* next-crypto
* Started merged patches and giving comments.
* ~55 patches.
* 2-3 new features from Marvell
* RX inject patchset for review.
* SSL/TLS patches for review.
* SM2 patches.
* main
* Updates to the MAINTAINERs file to help with automated delegation.
* Some updates to bit count helpers for Windows but affects other
trees as well.
* Patch for Atomics
* This needs review since it is an important API that will touch a lot of components later.
* https://patchwork.dpdk.org/project/dpdk/list/?series=29318
* Preparing for LTS release.
* Removing deprecated libraries.
* Meeting cancelled next week due to DPDK Summit.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backports ongoing. Awaiting test results.
Next LTS releases:
* 22.11.2 - Aug 31 set as release date. In validation.
* 21.11.5 - Released
* 20.11.9 - Released
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.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 over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15561 bytes --]
reply other threads:[~2023-09-07 10:43 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=PH8PR11MB6804CE4270DAB0259E3B572FFCEEA@PH8PR11MB6804.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).