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-01-26
Date: Thu, 26 Jan 2023 19:02:24 +0000	[thread overview]
Message-ID: <PH8PR11MB680458310DBBDCC586F57BF2FCCF9@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2023-01-26
=========================================

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

Participants:
* AMD
* Intel
* Nvidia
* Red Hat



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

The following are the proposed current dates for 23.03:


* V1:      25 December 2022
* RC1:      8 February 2023
* RC2:      1 March    2023
* RC3:      8 March    2023
* Release: 20 March    2023


Subtrees
--------

* next-net
  * Needs more reviews/support.
  * Focus is on ethdev reviews.
  * rte_flow has a lot of cleanup changes in this release and needs reviews
  * Some reviews ongoing but we are missing reviewer support on this tree.

* next-net-intel
  * No update.

* next-net-mlx
  * Some patches integrated and waiting to be pulled.
  * More in the backlog.

* next-net-mvl
  * No update

* next-eventdev
  * No update

* next-baseband
  * No update

* next-virtio
  * No update

* next-crypto
  * No update

* main
  * Thread API from Tyler under review
    * Waiting for ack on deprecation
  * Telemetry patches from Robin under review.
  * Two series on annotations.
  * Spurious failures in service-cores tests
  * testpmd fixes/additions need closer reviews




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

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

23.03
  * Proposal deadline (RFC/v1 patches): 25 December 2022
  * API freeze (-rc1): 8 February 2023
  * PMD features freeze (-rc2): 1 March 2023
  * Builtin applications features freeze (-rc3): 8 March 2023
  * Release: 20 March 2023

23.07
  * Proposal deadline (RFC/v1 patches): 15 April 2023
  * API freeze (-rc1): 31 May 2023
  * PMD features freeze (-rc2): 21 June 2023
  * Builtin applications features freeze (-rc3): 28 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

Other
-----

* TBA

LTS
---

Next releases will be:

* 22.11.1

* 21.11.4

* 20.11.8

* 19.11.15?
  * CVE and critical fixes only.


* Distros
  * v20.11 in Debian 11
  * Ubuntu 22.04 contains 21.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: 16884 bytes --]

                 reply	other threads:[~2023-01-26 19:02 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=PH8PR11MB680458310DBBDCC586F57BF2FCCF9@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).