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-06-16
Date: Thu, 16 Jun 2022 10:31:40 +0000	[thread overview]
Message-ID: <DM6PR11MB322792B51CBF21A72CFC3FA7FCAC9@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2022-06-16
=========================================

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

Participants:
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD


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

The following are the proposed current dates for 22.07:

* Proposal deadline (RFC/v1 patches): 10 April 2022
* API freeze (-rc1): 6 June 2022 - Actual 8 June
* PMD features freeze (-rc2): 23 June 2022 - Changed from 20 June
* Builtin applications features freeze (-rc3): 30 June 2022 - Changed from 27 June
* Release: 13 July 2022

Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates

Here are some provisional dates for 22.11:

* Proposal deadline (RFC/v1 patches): 14 August 2022
* API freeze (-rc1): 3 October 2022
* PMD features freeze (-rc2): 24 October 2022
* Builtin applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022

Subtrees
--------

* next-net
  * RC1 complete
  * Some more Testpmd and driver patches for after RC1

* next-net-intel
  * 3 patches waiting for upstream
  * 1 patch waiting for ARM's feedback on performance numbers

* next-net-mlx
  * Merged 7 patches
  * 1 other patchset being prepared for RC2
  * Also some fixes

* next-net-brcm
  * No update

* next-net-mrvl
  * ~ 15 patches in queue for RC2
  * Will submit PR Friday 17 June

* next-eventdev
  * 2 patches from Intel for RC2
  * Will submit PR Friday 17 June

* next-virtio
  * A lot of patches ready and preparing for RC2 PR
  * Work continuing on:
    * Patches for vHost Aync
    * Checksum offload
  * Large patchset for MLX5 is pending

* next-crypto
  * Applied around 20 patches
  * 20 more remaining for RC2
  * Patches on ipsec gateway that need reviews
  * Patch for adding CMAC to OpenSSL
  * Patch for Windows enablement of test application


* main
  * Working on fixes to vHost Crypto and IPsec unit tests
  * Cleanup series for memory leaks and NULL pointers need reviews:
    * https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
    * Will be merged if there are no reviews
  * Header split patchset
    * Non-RFC version merged but not yet enabled for all drivers
  * GCC 12 fixes
    * Merged patches agreed by Stephen and some other maintainers
  * Note there is an issue where compilation of the CNXK drivers
    is consuming too much memory, and time in the link stage:
    * https://mails.dpdk.org/archives/dev/2022-June/244227.html
    * If anyone has any suggestions let us know


LTS
---

Note, there is a proposal to merge security fixes to all 3 LTS branches
by August 28th.

* 21.11.2
  * Back porting ongoing
  * 21.11.1 released April 26th

* 20.11.6
  * Backporting waiting for Rc2
  * 20.11.5 released April 4th

* 19.11.13
  * Backporting waiting for Rc2
  * 19.11.12 released April 7th


* Distros
  * v20.11 in Debian 11
  * 22.04 will contain 21.11

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

If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.

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

                 reply	other threads:[~2022-06-16 10:31 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=DM6PR11MB322792B51CBF21A72CFC3FA7FCAC9@DM6PR11MB3227.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).