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 2023-11-16
Date: Thu, 16 Nov 2023 21:13:53 +0000	[thread overview]
Message-ID: <PH8PR11MB68049180055E4E0C38FC4CF5FCB0A@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2023-11-16
=========================================

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 working dates for 23.11:

* V1:      12 August   2023
* RC1:     11 October  2023
* RC2:      6 November 2023
* RC3:     13 November 2023
* RC4:     21 November 2023
* Release: 23 November 2023


The following are the current working dates for 24.03:

- Proposal deadline (RFC/v1 patches): 22 December 2023
- API freeze (-rc1): 5 February 2024
- PMD features freeze (-rc2): 23 February 2024
- Builtin applications features freeze (-rc3): 4 March 2024
- Release: 14 March 2024



Subtrees
--------

* next-net
  * RC3 released
  * Working on fixes.
    https://bugs.dpdk.org/show_bug.cgi?id=1326

* next-net-intel
  * Most fixes merged in RC3.
  * Some small fixes and docs pending for RC4.

* next-net-mlx
  * Some small fixes and docs pending for RC4.

* next-net-mvl
  * Merged in RC3.

* next-eventdev
  * Merged in RC3.

* next-baseband
  * PR sent.

* next-virtio
  * PR sent and merged in RC3.

* next-crypto
  * 3-4 fixes for RC4

* main
  * Move Experimental features older than 2 years to stable.
  * Waiting for latest version of DTS features.
  * Provisional dates for the next phases of the release:
    * RC4:     21 November 2023
    * Release: 23 November 2023


Proposed Schedule for 2023
--------------------------

See http://core.dpdk.org/roadmap/#dates


LTS
---

* 22.11.3 - In progress
* 21.11.6 - In progress
* 20.11.10 - In progress
* 19.11.15 - Will only be updated with CVE and critical fixes.


* Distros
  * Debian 12 contains DPDK v22.11
  * Ubuntu 22.04-LTS contains DPDK v21.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.



Drafts/Notes
-----

* 22.11.1  - Xueming
* 21.11.4  - Kevin
* 20.11.8  - Luca
* 19.11.15 - Christian

[-- Attachment #2: Type: text/html, Size: 15117 bytes --]

                 reply	other threads:[~2023-11-16 21:14 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=PH8PR11MB68049180055E4E0C38FC4CF5FCB0A@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).