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-08-17
Date: Thu, 24 Aug 2023 10:54:54 +0000	[thread overview]
Message-ID: <PH8PR11MB680401225E1BBE2AB25B84BBFC1DA@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2023-08-17
=========================================

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

Participants:
* AMD
* Intel
* Marvell
* Red Hat

Release Dates
-------------

The following are the proposed working dates for 23.11:

* V1:      12 August 2023
* RC1:     29 September 2023
* RC2:     20 October 2023
* RC3:     27 October 2023
* Release: 15 November 2023


Subtrees
--------

* next-net
  * New driver from Napatech
 * New driver RNP: https://patchwork.dpdk.org/project/dpdk/list/?series=29118
  * 1 other new driver

* next-net-intel
  * Some fixes merged.
  * Some patch sets for IDPF and CPF under rework.

* next-net-mlx
  * No update.

* next-net-mvl
  * 30-40 patches merged.
  * Almost everything reviewed.

* next-eventdev
  * 10 patched pending.

* next-baseband
  * Under review.

* next-virtio
  * Working on improvements for VDUSE.
  * Other patches under review.

* next-crypto
  * 50-55 patches.
 * 2-3 new features from Marvell
  * RX inject patchset for review.
  * SSL/TLS patches for review.
  * SM2 patches.
  * Merging not started yet.

* main
  * Busy with Windows.
  * Splitting EAL into two.
  * Cleanups for C11
  * New series for determining dependencies for unit tests. - Merged.
  * Working on build fixes.
  * 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): 29 September 2023
  * PMD features freeze (-rc2): 20 October 2023
  * Builtin applications features freeze (-rc3): 27 October 2023
  * Release: 15 November 2023


LTS
---

Backports ongoing. Awaiting test results.

Next LTS releases:

* 22.11.2 - Aug 31 set as release date.
* 21.11.5 - Testing reports received. Release in progress.
* 20.11.9 - Released
* 19.11.15
  * Will be updated with CVE and critical fixes only.


* 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/


Opens
-----

* None


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: 15407 bytes --]

             reply	other threads:[~2023-08-24 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 10:54 Mcnamara, John [this message]
2023-08-31  8:28 ` Mcnamara, John
  -- strict thread matches above, loose matches on Subject: below --
2023-08-17  8:48 Mcnamara, John

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