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 2022-11-24
Date: Thu, 24 Nov 2022 15:42:14 +0000 [thread overview]
Message-ID: <PH8PR11MB6804F9C3E95747CFDFAE273AFC0F9@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3027 bytes --]
Release status meeting minutes 2022-11-24
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 7 October 2022
* RC2: 28 October 2022
* RC3: 10 November 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Only doc fixes after RC4.
* next-net-intel
* Only doc fixes after RC4.
* next-net-mlx
* Only doc fixes after RC4.
* next-net-mvl
* Only doc fixes after RC4.
* next-eventdev
* Only doc fixes after RC4.
* next-virtio
* Only doc fixes after RC4.
* next-crypto
* Only doc fixes after RC4.
* main
* RC4 released.
* New next-bbdev tree created.
* Please note the proposed schedule for 2023 below
and respond if you have any concerns with the
dates.
Proposed Schedule for 2023
23.03
* Proposal deadline (RFC/v1 patches): 30 December 2022
* API freeze (-rc1): 10 February 2023
* PMD features freeze (-rc2): 24 February 2023
* Builtin applications features freeze (-rc3): 3 March 2023
* Release: 10 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 7 April 2023
* API freeze (-rc1): 26 May 2023
* PMD features freeze (-rc2): 16 June 2023
* Builtin applications features freeze (-rc3): 23 June 2023
* Release: 14 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 11 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 17 November 2023
LTS
---
Next releases will be:
* 21.11.3
* Backport patches have been sent.
* Merging of 22.11 patches in progress.
* 20.11.7
* Backport patches have been sent.
* Merging of 22.11 patches in progress.
* 19.11.14
* Backport patches have been sent.
* Merging of 22.11 patches in progress.
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialled for 19.11 to the 20.11 LTS cycle.
* 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: 16095 bytes --]
reply other threads:[~2022-11-24 15:42 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=PH8PR11MB6804F9C3E95747CFDFAE273AFC0F9@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).