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 2022-09-01
Date: Thu, 1 Sep 2022 08:58:02 +0000	[thread overview]
Message-ID: <DM6PR11MB32271A2EB500ED8EA007C0C3FC7B9@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2022-09-01
=========================================

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

Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD


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

The following are the proposed current dates for 22.11:

* V1 deadline: 24 August   2022 (previously 14 August)
* RC1:          3 October  2022 (subject to discussion)
* RC2:         23 October  2022
* RC3:         31 October  2022
* Release:     16 November 2022

Subtrees
--------

* next-net
  * New drivers in this release
    * Microsoft Azure Network Adapter (MANA) PMD
      * There are several RDMA implementation now.
      * Should we have RDMA bus driver?
    * Google Virtual Ethernet (GVE)
    * idpf (Infrastructure Data Path Function) PMD
    * net/qdma PMD
  * Work on removing deprecated flow API/code - needs acks from Intel
    * https://lore.kernel.org/all/20220812191827.3187441-1-ivan.malov@oktetlabs.ru/
  * Flow director clean-up merged

* next-net-intel
  * No update

* next-net-mlx
  * No update

* next-net-brcm
  * No update

* next-net-mrvl
  * Started merging patches
  * Reviews ongoing

* next-eventdev
  * Started merging patches
  * Reviews ongoing

* next-virtio
  * Around 30 patches in queue
  * Several vhost patches

* next-crypto
  * 3-35 patches merged
  * Patches for BBDev - needs review
  * Adding crypto security and sessions rework
  * Additional FIPs validation patches in this release

* main
  * New arch type: LoongArch
  * Proposed RC1 date (3 October) clashes with a national holiday
    in PRC (October 1st - ~October 7th). We may need to push RC1
    to October 10th, but that is late, so this needs some
    consideration/discussion.
  * DPDK EU summit next week.


Other
-----

* DPDK Summit: https://events.linuxfoundation.org/dpdk-userspace-summit/
  * Event Dates: Tuesday, September 6 - Thursday, September 8, 2022
  * Schedule: https://events.linuxfoundation.org/dpdk-userspace-summit/program/schedule/


LTS
---

Waiting for test results. Aiming for August 29th for all 3 LTSs.

* 21.11.2
  * Back porting in progress

* 20.11.6
  * Back porting in progress

* 19.11.13
  * Back porting in progress



* Distros
  * v20.11 in Debian 11
  * Ubuntu 22.04 contains 21.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. on https://meet.jit.si/DPDK

If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.

[-- Attachment #2: Type: text/html, Size: 15783 bytes --]

                 reply	other threads:[~2022-09-01  8:58 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=DM6PR11MB32271A2EB500ED8EA007C0C3FC7B9@DM6PR11MB3227.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).