From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Marchand, David" <david.marchand@redhat.com>
Subject: DPDK Release Status Meeting 2024-06-13
Date: Tue, 18 Jun 2024 10:42:58 +0000 [thread overview]
Message-ID: <PH8PR11MB68043F8BF996DC1434AEE121FCCE2@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2766 bytes --]
Release status meeting minutes 2024-06-13
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD [No]
* ARM
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 14 June 2024
- PMD features freeze (-rc2): 5 July 2024
- Builtin applications features freeze (-rc3): Mid July 2024 (TBC)
- Release: End July 2023 (TBC)
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Merged most of the ethdev patches.
* GENEVE one is remaining, I guess that is for next release.
* Napatech PMD reviewed, will wait for new version.
* Overall next-net is OK for -rc1.d
* next-net-intel
* Large ICE driver base code update submitted and waiting
review.
* next-net-mlx
* Almost completed for merge.
* Still working on one patchset.
* next-net-mvl
* PR ready.
* next-eventdev
* PR ready.
* next-baseband
* Prepared a pull request, there is one series which needs
a respin from Hernan.
* next-virtio
* Prepared a pull request (around 16 patches merged),
more patches need reviews and will go to rc2.
* next-crypto
* 2 PMDs to merge but should be ready for the PR.
* Awaiting some updates as requested from submitters.
* main
* Some series for Windows merged.
* Working on some respin patches.
* RC1 should be out Monday 17th June
* RC2 targeted for 5 July 2024
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - Released.
* 22.11.5 - Released.
* 21.11.7 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.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: 13944 bytes --]
reply other threads:[~2024-06-18 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=PH8PR11MB68043F8BF996DC1434AEE121FCCE2@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).