From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Marchand, David" <david.marchand@redhat.com>
Subject: DPDK Release Status Meeting 2023-10-26
Date: Thu, 26 Oct 2023 22:27:03 +0000 [thread overview]
Message-ID: <PH8PR11MB68049C847C98524540D1A858FCDDA@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2856 bytes --]
Release status meeting minutes 2023-10-26
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* 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 - Trending to 1 November
* RC3: 3 November 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* Eth_dev patches need to be finalized for RC2.
* 3 new drivers - not merged yet.
* Napatech driver will probably be in the next release
* next-net-intel
* Some fixes merged.
* next-net-mlx
* Some patches merged.
* ~45 patches for RC2
* next-net-mvl
* Prepping for RC2.
* next-eventdev
* Prepping for RC2.
* next-baseband
* Some patches ready
* Patches for new FPGA variant
* next-virtio
* Some fixes added and ready for pull.
* next-crypto
* ~10 patches in RC2 backlog.
* Merging in progress.
* main
* Looking at Windows patches.
* Series that need acks/reviews:
https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Series to mark experimental APIs as stable. Request for maintainers to
review an APIs that will move to stable.
* Regression in bitops API in RC1 - Fix merged.
* Reviews in progress for some of applications like DMA perf and ML dev test, and Pipeline.
* RC2 trending to November 1st.
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 - Trending to 1 November
* 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: 14760 bytes --]
reply other threads:[~2023-10-26 22:27 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=PH8PR11MB68049C847C98524540D1A858FCDDA@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).