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 2024-11-14
Date: Thu, 14 Nov 2024 10:04:37 +0000	[thread overview]
Message-ID: <PH8PR11MB680415E6D560AE3F3956741AFC5B2@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2024-11-14
=========================================

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

Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------

The following are the current/updated working dates for 24.11:

- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 19 October 2024
- PMD features freeze (-rc2): 12 November 2024
- Builtin applications features freeze (-rc3): targeted for 19 November 2024
- Release: targeted for 29 November 2024

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


Subtrees
--------

* next-net
  * Napatech driver merged.
  * Realtec driver merged.

* next-net-intel
  * Some fixes to merge in RC3.

* next-net-mlx
  * Some patches merged/planned for RC3.

* next-net-mvl
  * Some bug fixes to merge in RC3. ~8 patches.

* next-eventdev
  * 2 bug fixes to merge in RC3.

* next-baseband
  * Ready for RC3/release.

* next-virtio
  * Ready for RC3/release.

* next-crypto
  * 3-4 fix patches to merge.
  * ZTE driver deferred to next release.

* next-dts
  * Pydantic series merged.

* main
  * RC2 release on 12 November
  * Added improved announcement support.
  * Added Coverity fixes.
  * Merging Broadcom branch.
  * Merging DTS.
  * RC3 targeted for 19 November 2024
  * RC4 targeted for 26 November 2024
  * Release targeted for 29 November 2024



**Note**:
We will look to move this meeting to a US friendly time slot at
the start of November.


LTS
---

Status of the current LTSes

* 23.11.3 - In progress.
* 22.11.7 - In progress.
* 21.11.9 - In progress.

* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - 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 9: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: 13934 bytes --]

                 reply	other threads:[~2024-11-14 10:04 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=PH8PR11MB680415E6D560AE3F3956741AFC5B2@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).