From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: DPDK Release Status Meeting 2021-12-02
Date: Tue, 7 Dec 2021 08:42:48 +0000 [thread overview]
Message-ID: <DM6PR11MB32276016FEC07D780DC4EE13FC6E9@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
Release status meeting minutes 2021-12-02
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The discussion this week was mainly around release dates in the 3 release cycle. The following are the proposed dates for 22.03:
* 22.03 V1 2021-12-31
* 22.03 Merge 2022-02-11
* 22.03 Release 2022-03-11
And some provisional dates for the subsequent releases:
* 22.07 V1 2022-05-06
* 22.07 Merge 2022-06-10
* 22.07 Release 2022-07-15
* 22.11 V1 2022-09-09
* 22.11 Merge 2022-10-18
* 22.11 Release 2022-11-18
Subtrees
--------
* 21.11 released.
LTS
---
* There is a proposal to make 19.11 LTS into a 3 year release. This depends on companies providing testing for the additional releases:
* 21.11.1 in progress
* 20.11.4 in progress
* 19.11.11 in progress
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
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<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 12439 bytes --]
reply other threads:[~2021-12-07 8: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=DM6PR11MB32276016FEC07D780DC4EE13FC6E9@DM6PR11MB3227.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).