From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>
Subject: DPDK Release Status Meeting 2022-04-20
Date: Thu, 21 Apr 2022 16:02:35 +0000 [thread overview]
Message-ID: <DM6PR11MB3227455DA4D5EC258BE5CEFFFCF49@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3091 bytes --]
Release status meeting minutes 2022-04-20
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.07:
* Proposal deadline (RFC/v1 patches): 10 April 2022
* API freeze (-rc1): 30 May 2022
* PMD features freeze (-rc2): 20 June 2022
* Builtin applications features freeze (-rc3): 27 June 2022
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* Proposal deadline (RFC/v1 patches): 14 August 2022
* API freeze (-rc1): 3 October 2022
* PMD features freeze (-rc2): 24 October 2022
* Builtin applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Processing patches
* next-net-intel
* 15 patches ready for upstream - waiting for pull
* next-net-mlx
* Some patches ready to pull (by end of the week)
* next-net-brcm
* No update
* next-net-mrvl
* Around 15 patches in queue
* next-eventdev
* Around 15 patches in queue
* next-virtio
* Currently reviewing
* Async vhost patches - discussion ongoing
* Vitio block device Intel vdpa
* Waiting for new revisions
* next-crypto
* Starting merging some patches
* Will look at sync patches next week
* Test security app needs review
* main
* Merged some EAL patches
* Thread series for Windows
* Making progress
* Enabling of ASAN in the CI
* Making progress
* Found issue with CI
* https://bugs.dpdk.org/buglist.cgi?quicksearch=%5Basan%5D
* Lock annotations series:
* https://patchwork.dpdk.org/project/dpdk/list/?series=22292
* FreeBSD support for vmbus
* Cleanup series for memory leaks and NULL pointers need reviews:
* https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Sample apps being updated
* Header split patchset needs review
* http://patchwork.dpdk.org/project/dpdk/patch/20220402104109.472078-2-wenxuanx.wu@intel.com/
LTS
---
* 21.11.1
* RC1 for 21.11.1
* Looking for testing before April 13th
* Release targeted for April 26th
* 20.11.5
* Released April 4th
* 19.11.12
* Released April 7th
* Distros
* v20.11 in Debian 11
* 22.04 will contain 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. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 17369 bytes --]
reply other threads:[~2022-04-21 16:03 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=DM6PR11MB3227455DA4D5EC258BE5CEFFFCF49@DM6PR11MB3227.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.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).