DPDK patches and discussions
 help / color / mirror / Atom feed
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-10-28
Date: Tue, 28 Oct 2025 14:52:53 +0000	[thread overview]
Message-ID: <PH3PPF37F43E35D6A4015F36A3914DCE4DFFCFDA@PH3PPF37F43E35D.namprd11.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2540 bytes --]

Release status meeting minutes 2025-10-28
=========================================

Agenda:
- Release Dates
- Subtrees
- Roadmaps
- LTS
- Defects
- Opens

Participants:
- ARM
- Debian
- Intel
- Marvell
- Nvidia
- Red Hat
- Stephen Hemminger

Release Dates
-------------

The following are the proposed working dates for 25.11:

- Proposal deadline (RFC/v1 patches): 31 August 2025
- API freeze (-rc1): 24 October 2025
- PMD features freeze (-rc2): 7 November 2025
- Builtin applications features freeze (-rc3): 14 November 2025
- Release: 26 November 2025

See https://core.dpdk.org/roadmap/


Subtrees
--------

- next-net
  - Merged to RC1.
  - 36 patches pending.
  - 11 to review/merge.

- next-net-intel
  - 1 patch outstanding for RC2.

- next-net-mlx
  - No update.

- next-broadcom
  - No update.

- next-net-mvl
  - No update.

- next-eventdev
  - No update.

- next-baseband
  - PR ready.

- next-virtio
  - There is one fix for VDUSE that will be needed in rc2.

- next-crypto
  - Some Coverity fixes.

- next-dts
  - Due to merge Rx/Tx offload test suite.
    - Investigating CI issue.

- main
  - RC2 released 24 October 2025.
  - Some CI issues under investigation.
  - Outstanding work on PMU integration in trace.
  - Updated RC2/RC3 dates. See above.


Other
-----
  - None.

LTS
---

Released LTS versions:

- 24.11.3 - Released 2025-08-19
- 23.11.5 - Released 2025-08-25
- 22.11.9 - Released 2025-08-19
  - 22.11.10 released 2025-09-17 for CVE-2025-23259.


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: 13921 bytes --]

                 reply	other threads:[~2025-10-28 14:53 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=PH3PPF37F43E35D6A4015F36A3914DCE4DFFCFDA@PH3PPF37F43E35D.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).