From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Re: DPDK Release Status Meeting 2023-05-04
Date: Thu, 4 May 2023 09:25:25 -0700 [thread overview]
Message-ID: <20230504092525.2d32a19c@hermes.local> (raw)
In-Reply-To: <PH8PR11MB6804D2D5D4CAA8ED6B2BCEF2FC6D9@PH8PR11MB6804.namprd11.prod.outlook.com>
On Thu, 4 May 2023 10:24:45 +0000
"Mcnamara, John" <john.mcnamara@intel.com> wrote:
> Release status meeting minutes 2023-05-04
> =========================================
>
> Agenda:
> * Release Dates
> * Subtrees
> * Roadmaps
> * LTS
> * Defects
> * Opens
>
> Participants:
> * AMD
> * ARM
> * Intel
> * Marvell
> * Nvidia
> * Red Hat
>
>
> Release Dates
> -------------
>
> The following are the proposed current dates for 23.07:
>
> * V1: 22 April 2023
> * RC1: 31 May 2023
> * RC2: 21 June 2023
> * RC3: 28 June 2023
> * Release: 12 July 2023
>
>
> Subtrees
> --------
>
> * next-net
> * Under review.
> * ~120 patches in backlog.
> * GVE license update
>
> * next-net-intel
> * Starting to apply patches, about 20 patches are waiting for merge.
>
> * next-net-mlx
> * No update
>
> * next-net-mvl
> * Some patches merged.
> * ~30 patches remaining.
>
> * next-eventdev
> * Some patches merged.
> * AMD patches under review
>
> * next-baseband
> * No major features so far.
>
> * next-virtio
> * Intel series for port mirroring
> * Some concerns on code duplication and API complexity
> * Report of performance degradation in vhost driver
> * New series on guest notifications in slow path
> * VDUSE - Vhost VDPA in userspace. https://lwn.net/Articles/841054/
> * Under review
>
> * next-crypto
> * 60-70 patches in backlog
> * Patches to add new algorithms
> * Reviewing PDCP patches
> * Reviews and merges ongoing
>
> * main
> * Starting to merge patches to improve the Windows port
> * Reviewing ethdev patches
> * Patches from ARM for PMU
> * Postponed from last release
> * For tracing
> * Awaiting feedback on comments
> * Power Management feature from AMD
> * Memarea feature
> * CDX bus patches from AMD
> * Virtual PCI like bus
> * New checkpatch checks for atomic functions
> * Issues with Fedora 38 and GCC 13
> * Issue with Coverity automated analysis
> * Call for updates to the external Roadmap:
> https://core.dpdk.org/roadmap/
>
>
> 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): 31 May 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
> ---
>
> Next LTS releases will be:
>
> * 22.11.1
> * RC1 sent - Scheduled for May 5
> * 21.11.4
> * Got test feedback from Nvidia, Red Hat and Intel
> * 20.11.8
> * RC1 sent and first test report received
> * 19.11.15
> * 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/
Could we add current bugzilla statistics to the this status report?
prev parent reply other threads:[~2023-05-04 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 10:24 Mcnamara, John
2023-05-04 16:25 ` Stephen Hemminger [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=20230504092525.2d32a19c@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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).