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-12-14
Date: Thu, 14 Dec 2023 13:39:59 +0000	[thread overview]
Message-ID: <PH8PR11MB68045765ED9F45DF988D0E10FC8CA@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2023-12-14
=========================================

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

Participants:
* 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:     23 November 2023
* Release: 24 November 2023


The following are the current working dates for 24.03:

- Proposal deadline (RFC/v1 patches): 29 December 2023 (moved from 22 December)
- 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 on
  * Patches starting to arrive.

* next-net-intel
  * No updates this week.

* next-net-mlx
  * Roadmap sent.

* next-net-mvl
  * Starting to merge patches.
  * Roadmap sent.

* next-eventdev
  * Starting to merge patches.

* next-baseband
  * No updates this week.

* next-virtio
  * No updates this week.

* next-crypto
  * ~37 patches in backlog.

* main
  * V1 date moved to December 29th
  * New branch mirroring to GitHub to reduce load on git.dpdk.org.
  * Request for Roadmaps: https://core.dpdk.org/roadmap/
  * Looking for a new maintainer for the DMA device performance tool.


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

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


LTS
---

* 22.11.4 - In progress
* 21.11.6 - RC in progress
* 20.11.10 - Released.
* 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.

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

             reply	other threads:[~2023-12-14 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 13:39 Mcnamara, John [this message]
2023-12-15  0:43 ` fengchengwen
2023-12-15  9:24   ` Ferruh Yigit
2023-12-15  9:34     ` fengchengwen

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