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-dev] DPDK Release Status Meeting 2021-10-28
Date: Thu, 28 Oct 2021 13:35:02 +0000	[thread overview]
Message-ID: <SN6PR11MB3086D6BFFC33C6213F767385FC869@SN6PR11MB3086.namprd11.prod.outlook.com> (raw)

Release status meeting minutes 2021-10-28
=========================================

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

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


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

* v21.11 dates: http://core.dpdk.org/roadmap/#dates
  * PMD features freeze (-rc2): 5 November 2021
  * Builtin applications features freeze (-rc3): 12 November 2021
  * Release: 24 November 2021




Subtrees
--------

* next-net

  * RC1 merged and released
  * Still some patches to merge
  * One ethdev patch not merged
  * New NXT PMD - will need more changes
  * Should be ready for a new PR tomorrow Friday 29

* next-net-intel

  * More patches to be merged post RC1

* next-net-mlx

  * More patches to be merged post RC1

* next-net-brcm

  * More patches to be merged post RC1
  * Ready for a PR.

* next-net-mrvl

  * ~15 patches to be merged

* next-eventdev

  * Looking at series on telemetry support
  * Also a series from Ericsson under review but will probably move to next release
  * Doc update

* next-virtio

  * ~40 patches in the queue

  * Power monitor series from Intel - now ok

  * RSS series

  * 2 outstanding

    * Async support - needs reviews
    * Xilinx vdpa - at risk

* next-crypto

  * Security session postponed

  * IPsec under review

  * Telemetry merged

  * Windows cross compilation for MLX5 not working



* main

  * RC1 release on 25/10/2021

  * Second largest RC1 in DPDK history

  * Issue with Meson 6.0.0

    * See proposed fixes on patchwork

  * Interrupt series

    * Some issues/feedback on  mailing list
    * https://patchwork.dpdk.org/project/dpdk/list/?series=18664

  * Merging VFIO changes

  * PCI Series

    * Still under discussion
    * Probably won't make this release

  * Series for ARM on redefining wait schemes

    * https://patchwork.dpdk.org/project/dpdk/list/?series=19829
    * Should be ready for RC2

  * IWYU - Thomas will review

  * Some series changing API

    * Sched library



LTS
---

* v19.11 (next version is v19.11.10)
  * 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.

                 reply	other threads:[~2021-10-28 13:35 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=SN6PR11MB3086D6BFFC33C6213F767385FC869@SN6PR11MB3086.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).