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>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: DPDK Release Status Meeting 2023-10-05
Date: Thu, 5 Oct 2023 09:04:52 +0000	[thread overview]
Message-ID: <PH8PR11MB680488B0A20E543AC1C31D12FCCAA@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2023-10-05
=========================================

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

Participants:
* AMD
* 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:     27 October 2023
* RC3:      3 November 2023
* Release: 15 November 2023


Subtrees
--------

* next-net
  * Initial pull done.
  * Working on the rest of the tree.
  * There are still a number of rte_flow patches pending merge but not having
    reviews

* next-net-intel
  * No update

* next-net-mlx
  * No update

* next-net-mvl
  * Will send PR today

* next-eventdev
  * Sent PR

* next-baseband
  * Reviewing patches for VRB2 series.

* next-virtio
  * Other patches under review.

* next-crypto
  * 3 series pending PR - will be complete by the end of the week
  * 2-3 new features from Marvell
  * RX inject patchset for review.
  * SSL/TLS patches for review.
  * SM2 patches need ack

* main
  * Patch for Atomics merged.
    * Some additions/changes needed in RC2.
  * Reviewing dispatcher library - new library approved by tech board.
  * Working on Control Threads
  * PCI API cleanup merged. Subtrees take note.
  * Preparing for LTS release.
  * Removing deprecated libraries.



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

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

23.11

  * Proposal deadline (RFC/v1 patches): 12 August 2023
  * API freeze (-rc1): 11 October 2023
  * PMD features freeze (-rc2): 27 October 2023
  * Builtin applications features freeze (-rc3): 3 November 2023
  * Release: 15 November 2023


LTS
---

LTS in the current cycle have been released.

* 22.11.2 - Released
* 21.11.5 - Released
* 20.11.9 - Released
* 19.11.15
  * Will only be updated with CVE and critical fixes.


* Distros
  * v22.11 in Debian 12
  * Ubuntu 22.04-LTS contains 21.11
  * Ubuntu 23.04 contains 22.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: 14702 bytes --]

             reply	other threads:[~2023-10-05  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  9:04 Mcnamara, John [this message]
2023-10-09 13:17 ` Ferruh Yigit

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