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-06-15
Date: Thu, 15 Jun 2023 17:59:24 +0000	[thread overview]
Message-ID: <PH8PR11MB6804CD12239C37A4D19B181AFC5BA@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2023-06-15
=========================================

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

Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat


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

The following are the proposed current dates for 23.07:

* V1:      22 April 2023
* RC1:     13  June 2023
* RC2:     23  June 2023 - Moved from 21
* RC3:     30  June 2023 - Moved from 28
* Release: 12  July 2023


Subtrees
--------

* next-net
  * Looking at larger patches from SFC and Netronome.

* next-net-intel
  * Mostly merged for RC1.

* next-net-mlx
  * No update.

* next-net-mvl
  * 20 patches merged and ready for RC2.

* next-eventdev
  * 3 patches merged and ready for RC2.

* next-baseband
  * Some discussion on API/ABI changes in BBDev.

* next-virtio
  * Some patches, mostly fixes, under review.
  * Majority of the larger features merged in RC1.

* next-crypto
  * Comments on some of the patches for RC2: needs review
    * MLX5 crypto driver.
    * OpenSSL and QAT: from Kai
  * Some compilations issue on IPsecMB blocking merge.

* main
  * RC1 is out.
  * Graph series has a new revision.
  * Meson build script updates.
  * Patch from Bruce on tracing/logging
  * PCIe maintainership

  * Overall we need more maintainers and/or more trees
    * Trees for graph and pipeline
    * Tree for core and other




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

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

23.07
  * Proposal deadline (RFC/v1 patches): 22 April 2023
  * API freeze (-rc1): 7 June 2023
  * PMD features freeze (-rc2): 23 June 2023
  * Builtin applications features freeze (-rc3): 30 June 2023
  * Release: 12 July 2023

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

Backporting in progress.

Next LTS releases:

* 22.11.2
* 21.11.5
* 20.11.9
* 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: 16270 bytes --]

                 reply	other threads:[~2023-06-15 17:59 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=PH8PR11MB6804CD12239C37A4D19B181AFC5BA@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).