DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: DPDK Release Status Meeting 2022-05-05
Date: Mon, 9 May 2022 19:39:29 +0000	[thread overview]
Message-ID: <DM6PR11MB32278D920ED32D35FD16FD8CFCC69@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)

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

Release status meeting minutes 2022-05-05
=========================================

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

Participants:
* ARM
* Intel
* Debian/Microsoft
* 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): 30 May 2022
* PMD features freeze (-rc2): 20 June 2022
* Built-in applications features freeze (-rc3): 27 June 2022
* 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
* Built-in applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022

Subtrees
--------

* next-net
  * Moving forward with merging patches

* next-net-intel
  * 18 patches ready for merge

* next-net-mlx
  * Some patches pushed to next-net

* next-net-brcm
  * No update

* next-net-mrvl
  * 20 patches merged
  * 14 patches in queue

* next-eventdev
  * 20+ patches merged under review or pending merge

* next-virtio
  * Fixing checksum bugs in virtio
  * New version of Async vhost patches - getting closer to merge

* next-crypto
  * 30 patches merged and 20 ready to be merged
  * New PMD from Atomic Rules

* main
  * Looking at Thread patch series for Windows
      * Progressing - needs reviews
  * Enabling of ASAN in the CI
      * Some blocking issues
   * Fix sent by Anatoly
  * Lock annotations series:
    * https://patchwork.dpdk.org/project/dpdk/list/?series=22292
    * Needs docs and remerge after Maxime's changes
  * Cleanup series for memory leaks and NULL pointers need reviews:
    * https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
  * Sample apps being updated
  * Header split patchset needs review
    * http://patchwork.dpdk.org/project/dpdk/patch/20220402104109.472078-2-wenxuanx.wu@intel.com/
  * Docs fix for ETH and VLAN flow items in Support Matrix from Ilya needs review/merge
    * https://patchwork.dpdk.org/project/dpdk/patch/20220316120157.390311-1-i.maximets@ovn.org/
  * Public meeting on: ethdev: datapath-focused meter actions
    * http://mails.dpdk.org/archives/dev/2022-April/239961.html




LTS
---

* 21.11.1
  * Released April 26th

* 20.11.5
  * Released April 4th

* 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: 17713 bytes --]

                 reply	other threads:[~2022-05-09 19:39 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=DM6PR11MB32278D920ED32D35FD16FD8CFCC69@DM6PR11MB3227.namprd11.prod.outlook.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    /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).