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-21
Date: Wed, 27 Oct 2021 15:53:41 +0000	[thread overview]
Message-ID: <SN6PR11MB30863C60D980493B69616AF2FC859@SN6PR11MB3086.namprd11.prod.outlook.com> (raw)

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

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

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


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

* v21.11 dates
  * Proposal/V1:    Friday, 10 September (complete)
  * -rc1:           Friday, 15 October - Moved to Monday 25 October
  * Release:        Friday, 19 November


Subtrees
--------

* next-net

  * Subtrees pulled

  * Most patches are in

  * Ethdev patchset from Intel still iterating

  * 2 Series from Nvidia around eth_dev, can go in after RC1

  * Other eth_dev patches reviewed

  * Some testpmd patches still to be reviewed

  * Series should be ready Friday 22

* next-net-intel

  * Mainly merged up

* next-net-mlx

  * Some patch pulled
  * Need to push fix for eal interrupts

* next-net-brcm

  * 1 patchset on patchwork
  * Will need a v2. Probably after RC1

* next-net-mrvl

  * Almost all patches merged and pulled
  * A few minor ones to be checked

* next-eventdev

  * PR submitted

* next-virtio

  * Started to apply patches
  * PR hopefully ready today
  * Not all series will be in this series

* next-crypto

  * Merged ipsec changes

  * Maybe some compilation  issues

  * 2 library changes pending



* main

  * Interrupt series

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

  * Series to rename mbuf flags - API cleanup

  * PCI Series

   - Still under discussion

  * Series for ARM on redefining wait schemes

    - https://patchwork.dpdk.org/project/dpdk/list/?series=19829

  * Series for new pdump design

  * DMA library merged. PMDs under review.

  * New Slack channel: https://join.slack.com/t/dpdkproject/shared_invite/zt-v6c9ef5z-FqgOAS7BDAYqev_a~pbXdw




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 Thursdays 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-27 15:54 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=SN6PR11MB30863C60D980493B69616AF2FC859@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).