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>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: DPDK Release Status Meeting 2021-11-11
Date: Fri, 12 Nov 2021 16:19:54 +0000	[thread overview]
Message-ID: <DM6PR11MB3227F4F3585C0490C2518509FC959@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2021-11-11
=========================================

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

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


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

* v21.11 dates: http://core.dpdk.org/roadmap/#dates
  * Built-in applications features freeze (-rc3): 16 November 2021
  * Release: 24 November 2021



* Proposed dates for 22.02

  * Proposal deadline (RFC/v1 patches): 14 December 2021

  * API freeze (-rc1): 14 January  2022

  * PMD features freeze (-rc2): 28 January  2022

  * Built-in applications features freeze (-rc3): 18 February 2022

  * Release:  22 February 2022



* There is also a proposal to have only 3 releases in 2022:

  *  22.03, 22.07, 22.11


Subtrees
--------

* next-net

  * Pulled from subtrees

  * Waiting for some updates

  * I40e descriptor fix

  * - 20% performance drop on ARM  platforms
    - Needs some discussion

* next-net-intel

  * Tree mostly closed.

* next-net-mlx

  * Some fixes coming for
  * Updates required for build issues

* next-net-brcm

  * No update.

* next-net-mrvl

  * 2 patches for merging

* next-eventdev

  * 3 patches merged
  * Working on doc changes

* next-virtio

  * Xilinx vdpa driver - new    version sent for review
  * Some fix patches to be merged

* next-crypto

  * Fixes under review

  * Xilinx vdpa driver - merged



* main

  * Rc2 released on 2021-11-09

  * New driver for DMA

  * GPU/CUDA library to be merged

  * Issues with Clang 13 on Fedora 35

  * Need to enable ASAN in CIs

  * L3FWD - series that changes the IP addresses

  * Interrupt series merged

  * DMA drivers to merge

  * DMARC mitigation has happened for dpdk.org's mailing lists
    https://mails.dpdk.org/archives/announce/2021-September/000385.html



LTS
---



* There is a proposal to make 19.11 LTS into a 3 year release

* 20.11.3 released on Monday Sept 6

* 19.11.10 released on Monday Sept 6



* Distros
  * v20.11 in Debian 11

  * v20.11 in Ubuntu 21.04




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 8:30 UTC. on https://meet.jit.si/DPDK

If you wish to attend 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: 20196 bytes --]

                 reply	other threads:[~2021-11-12 16:20 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=DM6PR11MB3227F4F3585C0490C2518509FC959@DM6PR11MB3227.namprd11.prod.outlook.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).