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-04-15
Date: Wed, 16 Apr 2025 14:53:38 +0000	[thread overview]
Message-ID: <PH8PR11MB680470573A118EAE462E3127FCBD2@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2025-04-15
=========================================

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

Participants:
* Broadcom
* ARM
* Debian
* Intel
* Marvell
* Microsoft
* Nvidia
* Red Hat


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

The following are the proposed working dates for 27.03:

- Proposal deadline (RFC/v1 patches): 20 April 2025
- API freeze (-rc1): 30 May 2025 - Moving to June 4
- PMD features freeze (-rc2): 20 June 2025 - Moving to 25
- Builtin applications features freeze (-rc3): 27 June 2025 - Moving to July 2
- Release: 11 July 2025

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


Subtrees
--------

* next-net
  * ~70 patches pending and around 16 waiting for review.

* next-net-intel
  * ~10 patches, mainly deferred from last release.
  * 2-3 new features

* next-net-broadcom
  * Gathering patches for this release.

* next-net-mlx
  * No updates this week.

* next-net-mvl
  * Anticipate 20-30 patches
  * Review and merge in progress.

* next-eventdev
  * ~20 patches
  * Review and merge in progress.

* next-baseband
  * No patches at the moment.

* next-virtio
  * 1 fix and some patch series pending.

* next-crypto
  * 20+ patches pending.
  * New crypto driver for ZTE
  * New Algorithm: Snow 5G

* next-dts
  * 20+ patches.

* main
  * Testpmd now builds in the CI with MSVC
  * License check approved.
  * Merged symbol export series. This will affect all patches
    that aren't merged yet and which touch the version map files.
    Please rebase your patches and resubmit. David Marchand
    can help.
  * Looking for updates to the roadmap file.
  * The following milestone dates will move by a few days:
    - (-rc1): 30 May  2025 - Moving to 4  June
    - (-rc2): 20 June 2025 - Moving to 25 June
    - (-rc3): 27 June 2025 - Moving to 2  July


Other
-----
  - DPDK Summit 2025 will be in Prague in May 8-9:
    - https://events.linuxfoundation.org/dpdk-summit/
    - https://www.dpdk.org/event/dpdk-summit-2025-prague/


LTS
---

Testing in progress. Ongoing LTS versions:

* 24.11.2
* 23.11.4
* 22.11.8 - Released

Test results are coming in. Still waiting for some validation.

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 24.04 contains DPDK v23.11
  * Ubuntu 23.04 contains DPDK v22.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: 16107 bytes --]

                 reply	other threads:[~2025-04-16 14:54 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=PH8PR11MB680470573A118EAE462E3127FCBD2@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).