From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
Tomasz Duszynski <tduszynski@marvell.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>, nd <nd@arm.com>
Subject: RE: DPDK Release Status Meeting 2023-06-01
Date: Fri, 2 Jun 2023 09:45:15 +0000 [thread overview]
Message-ID: <AS8PR08MB708093718E77CFE6E43E7EA69E4EA@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <PH8PR11MB68046C12FC5D8D6CB1B2269DFC499@PH8PR11MB6804.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2584 bytes --]
From: Mcnamara, John <john.mcnamara@intel.com>
Sent: Thursday, June 1, 2023 11:42 PM
To: dev@dpdk.org
Cc: thomas@monjalon.net; david.marchand@redhat.com
Subject: DPDK Release Status Meeting 2023-06-01
Release status meeting minutes 2023-06-01
=========================================
<snip>
* main
* Starting to merge patches to improve the Windows port
* Reviewing ethdev patches
* Patches from ARM for PMU
[Ruifeng] This is a series [1] contributed Tomasz (on copy) from Marvell.
Hi Tomasz,
Hope you are working on the comments. Thanks.
[1] https://patchwork.dpdk.org/project/dpdk/cover/20230216175502.3164820-1-tduszynski@marvell.com/
* Postponed from last release for tracing
* Awaiting feedback on comments - will be deferred if no replies.
* Power Management feature from AMD
* CDX bus patches from AMD
* Virtual PCI like bus
* Issues with Fedora 38 and GCC 13
* Fixes merged
* Issues with Intel lab CI reporting false positives
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 7 June 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
LTS
---
* 22.11.1
* Released on May 7
* 21.11.4
* Released May 17
* 20.11.8
* Released on April 27
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* 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/
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<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 13473 bytes --]
prev parent reply other threads:[~2023-06-02 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 15:42 Mcnamara, John
2023-06-02 9:45 ` Ruifeng Wang [this message]
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=AS8PR08MB708093718E77CFE6E43E7EA69E4EA@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=nd@arm.com \
--cc=tduszynski@marvell.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).