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-01-28
Date: Tue, 28 Jan 2025 15:01:22 +0000	[thread overview]
Message-ID: <PH8PR11MB680466C3476BF3419B9226BCFCEF2@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

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

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

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


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

The following are the proposed working dates for 25.03:

- Proposal deadline (RFC/v1 patches): 4 January 2025
- API freeze (-rc1): 7 February 2025
- PMD features freeze (-rc2): 28 February 2025
- Builtin applications features freeze (-rc3): 7 March 2025
- Release: 26 March 2025


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


Subtrees
--------

* next-net
  * No update.

* next-net-intel
  * Several patches merged on intel tree
  * Patch to deduplicate Intel driver code
  * ~ 15 patches on the backlog
  * Expecting a large patch to the igc/e1000

* next-net-mlx
  * Some patches merged.
  * No big changes in this release.

* next-net-mvl
  * Some patches merged.
  * 5 patches remaining.

* next-eventdev
  * Some patches merged.
  * 5 patches remaining.

* next-baseband
  * 1 series submitting. Awaiting review.

* next-virtio
  * 1 PR merged to fix regression.
  * Backlog of patches to review.

* next-crypto
  * ~30 patches on backlog
  * Series on ZTE driver
  * Issue with checkpatch

* next-dts
  * 34 patches in backlog. Around the same number merged.
  * Issue with Python 3.13

* main
  * The meeting has moved to a US friendly time slot on Tuesdays
  * Merging patches from Microsoft/Windows.
    - Packed attributes
    - Changes for MSVC
  * next-net merged
  * New driver for XSC from Yunsilicon
  * Some fixes have been merged to main to fix
    GCC 15 issues.


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


LTS
---

Current LTS versions:

* 24.11.2
* 23.11.3
* 22.11.7

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

                 reply	other threads:[~2025-01-28 15:02 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=PH8PR11MB680466C3476BF3419B9226BCFCEF2@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).