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-14
Date: Wed, 15 Jan 2025 14:35:45 +0000	[thread overview]
Message-ID: <PH8PR11MB68047AFC1CFB93085F798729FC192@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

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

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

Participants:
* ARM
* Intel
* Marvell
* 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: 14 March 2025


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


Subtrees
--------

* next-net
  * RC4 released.

* next-net-intel
  * Nothing applied yet.
  * Base code updates planned.
  * Also patchset on code deduplication and maybe
    dir restructuring.

* next-net-mlx
  * No update.

* next-net-mvl
  * No update.

* next-eventdev
  * No update.

* next-baseband
  * No patches as yet.

* next-virtio
  * Some series and patches in queue.

* next-crypto
  * Some patches in queue.
  * ZTE compressdev driver.
  * Patches for virtio net and crypto.
    Will be merged first in next-virtio

* next-dts
  * Roadmap on track.

* main
  * The meeting has moved to a US friendly time slot on Tuesdays
  * A lot of patches from Microsoft/Windows.
  * Big VLA series.
  * The following are the proposed dates for DPDK 25.03:
    RC1: Feb 7
    RC2: Feb 28
    RC3: Mar 7
    RC4: Mar 14
    Rel: Mar 21


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


LTS
---

Current LTS versions:

* 23.11.3.
* 22.11.7.
* 21.11.9.

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 Thursday 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: 14411 bytes --]

             reply	other threads:[~2025-01-15 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15 14:35 Mcnamara, John [this message]
2025-01-17  9:49 ` Mcnamara, John

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=PH8PR11MB68047AFC1CFB93085F798729FC192@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).