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 2025-05-27
Date: Tue, 27 May 2025 13:58:45 +0000 [thread overview]
Message-ID: <PH8PR11MB68047B22F8D2DE1374D46B61FC64A@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2667 bytes --]
Release status meeting minutes 2025-05-27
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* Broadcom
* ARM
* Intel
* Marvell
* Microsoft
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 25.07:
- Proposal deadline (RFC/v1 patches): 20 April 2025
- API freeze (-rc1): 4 June 2025
- PMD features freeze (-rc2): 25 June 2025
- Builtin applications features freeze (-rc3): 2 July 2025
- Release: 11 July 2025
See https://core.dpdk.org/roadmap/
Subtrees
--------
* next-net
* 190 patches ready for merge.
* Will start to merge to main tomorrow.
* next-net-intel
* 24 patches merged and pulled.
* next-net-broadcom
* No updates this week.
* next-net-mlx
* ~20~ to be merged.
* Ready for pull.
* next-net-mvl
* Patches ready for merge by Friday.
* next-eventdev
* Waiting for some Intel PMD patches.
* next-baseband
* Tree has been pulled.
* next-virtio
* Tree has been pulled.
* next-crypto
* Patches have been merged and ready to pull.
* New crypto driver for ZTE
* New Algorithm: Snow 5G
* next-dts
* Some patches merged.
* Planned API changes that were discussed at the summit
will move to next release.
* main
* Trees are starting to be pulled for RC1.
* Patches from Microsoft for EAL and memory.
* DPDK Bay Area Summit - Santa Clara, CA
https://www.dpdk.org/event/dpdk-bay-area-summit-santa-clara-ca-september-17-18-2025/
Other
-----
- None.
LTS
---
Released LTS versions:
* 24.11.2
* 23.11.4
* 22.11.8
See https://core.dpdk.org/roadmap/#dates
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.14 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 25.04 contains DPDK v24.11
* Ubuntu 24.04 LTS contains DPDK v23.11
* RHEL 8/9 contains DPDK 23.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 Tuesday at 14:30 DST 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: 14656 bytes --]
reply other threads:[~2025-05-27 13:58 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=PH8PR11MB68047B22F8D2DE1374D46B61FC64A@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).