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-09-16
Date: Fri, 17 Sep 2021 15:32:57 +0000	[thread overview]
Message-ID: <BYAPR11MB3078A40796291A79A94D8DB6FCDD9@BYAPR11MB3078.namprd11.prod.outlook.com> (raw)

Release status meeting minutes 2021-09-16
=========================================

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

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


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

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


Subtrees
--------

* main
  * Oops/core dump handling
  * Windows: new API for thread management
  * Will review new version of DMA dev
  * New Slack channel: https://join.slack.com/t/dpdkproject/shared_invite/zt-v6c9ef5z-FqgOAS7BDAYqev_a~pbXdw

* next-net
  * Reviews and merging ongoing
  * Lot of Ethdev patches - concerning due to number and to conflicts
  * Will merge from sub-trees today

* next-net-brcm
  * Patches have been merged to subtree

* next-net-intel
  - Reviews and merging ongoing

* next-net-mlx
  - 24 patches on the list that need to reviewed merged

* next-net-mrvl
  - Some patches merged.
  - 50-60 other patches
  - Ready to merge

* next-crypto
  * Merged ~50 patches
  * Has been pulled by Thomas

* next-eventdev
  * Some patches from Intel under review with comments
  * Driver patches for cxnk
  * Changes on API hiding (for ABI stability)

* next-virtio
  * Reviewing patches and  submitted first PR
  * Maxime submitting virtio RSS feature
  * 30 Patches on list, many around Vhost async
  * Xilinx driver reviewed
  * Power management patches  under review
  * DMA Device RFC under review
    * Comments from Ilya on the OVS list that functionality may below in DPDK rather than OVS:  http://patchwork.ozlabs.org/comment/2751918/


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
-----

* Release of OpenSSL 3.0 will cause some compilation issues in cryptodev: https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/


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-09-17 15:33 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=BYAPR11MB3078A40796291A79A94D8DB6FCDD9@BYAPR11MB3078.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).