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-03-28
Date: Thu, 28 Mar 2024 11:30:39 +0000	[thread overview]
Message-ID: <PH8PR11MB68047F4B944503C07B6E3F96FC3B2@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2024-03-28
=========================================

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.03:

* V1:      29 December 2023
* RC1:     21 February 2024
* RC2:      8 March    2024
* RC3:     15 March    2024
* Release: 27 March    2024


  * 24.07 Proposed dates:
    - Proposal deadline (RFC/v1 patches): 26 April 2024
    - API freeze (-rc1): 7 June 2024
    - PMD features freeze (-rc2): 21 June 2024
    - Builtin applications features freeze (-rc3): 28 June 2024
    - Release: 10 July 2023

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


Subtrees
--------

* next-net
  * Complete for RC4/Release.

* next-net-intel
  * Complete for RC4/Release.

* next-net-mlx
  * Complete for RC4/Release.

* next-net-mvl
  * Complete for RC4/Release.

* next-eventdev
  * Complete for RC4/Release.

* next-baseband
  * Complete for RC4/Release.

* next-virtio
  * Complete for RC4/Release.

* next-crypto
  * Complete for RC4/Release.


* main
  * Working on release notes and final documentation fixes.
  * Target release March 28th.

  * 24.07 Proposed dates:
    - Proposal deadline (RFC/v1 patches): 26 April 2024
    - API freeze (-rc1): 7 June 2024
    - PMD features freeze (-rc2): 21 June 2024
    - Builtin applications features freeze (-rc3): 28 June 2024
    - Release: 10 July 2023




LTS
---

Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/

* 23.11.1 - In progress.
* 22.11.5 - In progress.
* 21.11.7 - 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-LTS will contain DPDK v23.11
  * Ubuntu 23.04 contains DPDK v22.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 UTC 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: 14476 bytes --]

                 reply	other threads:[~2024-03-28 11:30 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=PH8PR11MB68047F4B944503C07B6E3F96FC3B2@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).