DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: DPDK Release Status Meeting 2023-05-11
Date: Thu, 11 May 2023 13:57:20 +0000	[thread overview]
Message-ID: <PH8PR11MB6804040F68F0ED91F679BB59FC749@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3671 bytes --]

Release status meeting minutes 2023-05-11
=========================================

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 updated from MIT to FreeBSD

* next-net-intel
  * Some patches are waiting for merge and some under review.
  * Seeking community input on adapting DPDK to P4 Runtime backend:
    http://mails.dpdk.org/archives/dev/2023-May/267719.html

* 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 patches in this release.

* next-virtio
  * Reviews ongoing
  * 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
    * Fixes merged

  * Call for updates to the external Roadmap:
    https://core.dpdk.org/roadmap/


* Static code analysis


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
  * Released on May 7
* 21.11.4
  * Some issues found in Intel testing - under investigation.
* 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/



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: 18228 bytes --]

                 reply	other threads:[~2023-05-11 13:57 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=PH8PR11MB6804040F68F0ED91F679BB59FC749@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).