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-11-010
Date: Fri, 11 Nov 2022 11:21:08 +0000	[thread overview]
Message-ID: <PH8PR11MB68049C8AA33AC85C4F39643AFC009@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2022-11-10
=========================================

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

Participants:
* ARM [No]
* Canonical [No]
* 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
* RC1:          7 October  2022
* RC2:         28 October  2022
* RC3:         14 November 2022
* RC4:         18 November 2022
* Release:     23 November 2022

Subtrees
--------

* next-net
  * Mainly fixes from now on.
  * Still a lot of patches and waiting on reviews
  * Some outstanding for testpmd, memif and request from Intel to help review.

* next-net-intel
  * Needs additional time for RC3 as there are still have P2 bug fixes to be reviewed.
  * There are alos bug fixes on dpdk-next-net-intel tree waiting for merge.

* next-net-mlx
  * Closing on patches. Bug fixes only for RC3.

* next-net-mrvl
  * No new patches.

* next-eventdev
  * Pull request sent to Thomas.

* next-virtio
  * Pull request sent to Thomas.

* next-crypto
  * 20 fixes applied with some more to apply.
  * Will be ready later today/tomorrow for Pull Request

* main
  * RC2 released on November 1.
  * Mempool stats - no response from Mailing List as to whether it needs to be in RC3 or not.
    * Ok to merge in this release.
    * Will need additional testing.
    * Request to Intel team to test.
  * DMA perf app - still has RFC tags.
    * need confirmation in Intel [RFC v5] app/dma-perf: introduce dma-perf application
    * OK for 22.03.
  * RC3/RC4 and Release dates have changed. See above.

LTS
---

Next releases will be:

* 21.11.3
  * Backport patches have been sent
  * Some in progress

* 20.11.7
  * Backport patches have been sent
  * Some in progress

* 19.11.14
  * Backport patches have been sent
  * Some in progress

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 over Jitsi on https://meet.jit.si/DPDK

You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.



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

                 reply	other threads:[~2022-11-11 11:21 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=PH8PR11MB68049C8AA33AC85C4F39643AFC009@PH8PR11MB6804.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).