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>,
	"Marchand, David" <david.marchand@redhat.com>
Subject: DPDK Release Status Meeting 2024-10-03
Date: Thu, 3 Oct 2024 10:43:46 +0000	[thread overview]
Message-ID: <PH8PR11MB6804D039D15ABC203F6227E9FC712@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2024-10-03
=========================================

Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens

Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat


Release Dates
-------------

The following are the current/updated working dates for 24.11:

- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 7 October 2024 - Update: Friday 11 October
- PMD features freeze (-rc2): 28 October 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023

https://core.dpdk.org/roadmap/#dates


Subtrees
--------

* next-net
  * Working on Ethdev
    - Some merged.
    - Some patches from previous release.
    - Some ethdev patches will be merged after RC1
  * 2 New PMD: net/sxe, net/xsc - under review
  * 2 Updating: net/r8169, net/zxdh. Also Napatech: net/ntnic.

* next-net-intel
  * 4 base code updates applied.
  * ~ 70 patches on tree
  * Ready for merge.

* next-net-mlx
  * No updates this week.

* next-net-mvl
  * Around 40 patches under review.
  * Some patches merged and some in progress.
  * Will send PR next week

* next-eventdev
  * Around 10 patches under review.
  * Two specification changes from Intel and Marvell
  * Merging has started.

* next-baseband
  * Almost ready for PR
  * 1 other series under review for merge.

* next-virtio
  * Almost ready for PR
  * Other patches can go in RC2

* next-crypto
  * 60 patches in queue.
  * Some PMD fixes merged.
  * New PMD from ZTE for compression and crypto.
  * Some new APIs and changes to APIs.
  * The series on "cryptodev: replace LIST_END enumerators with APIs" needs review:
    https://patches.dpdk.org/project/dpdk/patch/20240905101438.3888274-1-gakhil@marvell.com/

* next-dts
  * Capabilities merged.
  * Working through roadmap patches.

* main
  * IPv6 patchset to review
  * Series on "VFIO hotplug with multiprocess" needs review.
    https://patchwork.dpdk.org/project/dpdk/list/?series=33028
  * Big series cleaning up logs in drivers.
  * RC1 will move to Friday 11 October


LTS
---

Status of the current LTSes

* 23.11.2 - Released.
* 22.11.6 - Released.
* 21.11.8 - Released.

* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.


* Distros
  * Debian 12 contains DPDK v22.11
  * Ubuntu 24.04 contains DPDK v23.11
  * Ubuntu 23.04 contains DPDK v22.11
  * RHEL 8/9 contains DPDK 23.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 DST 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: 15343 bytes --]

                 reply	other threads:[~2024-10-03 10:43 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=PH8PR11MB6804D039D15ABC203F6227E9FC712@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).