DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 06/05/2021
Date: Thu, 6 May 2021 13:07:53 +0100	[thread overview]
Message-ID: <YJPcCpt6M4oS5uaL@silpixa00399752> (raw)

Release status meeting minutes {Date}
=====================================
:Date: 6 May 2021
:toc:

.Agenda:
* Release Dates
* -rc2 status
* Subtrees
* LTS
* Defects
* Opens

.Participants:
* Arm
* Broadcom
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat


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

* `v21.05` dates
  - -rc2 is released on Wednesday, 5 May
    ** http://inbox.dpdk.org/dev/3585896.ctXz43JjJv@thomas/
  - -rc3:           Wednesday, 12 May
  - -rc4:           Tuesday, 18 May
  - Release:        Friday, 21 May

* `v21.08` draft dates (updated), please comment:
  - Proposal/V1:    Wednesday, 2 June
  - -rc1:           Monday, 5 July
  - Release:        Tuesday, 3 August

* Expecting a small `v21.08` release.


rc2 status
----------

* The -rc2 is so new, no test reports yet.

* Good to get more test results, please share the test reports


Subtrees
--------

* main
  - example, tooling and fix patches in the backlog
  - i40e/iavf PF reset issue adding new bus/pci API, it may be later for this release
    ** Is the fix critical for this release?

* next-net
  - 'ena' PMD base code update and fix patches are in backlog

* next-crypto
  - All merged except mlx crypto PMD and crypto unit test refactor
    ** mlx crypto PMD, will review it today and merge it for -rc3 if all good
    ** crypto unit test refactor is causing segfault
       *** Working on it
  - NXP baseband driver is postponed to next release
  - Fixes will be merged for -rc3

* next-eventdev
  - Fixes as they arrive

* next-virtio
  - Backlog is clean, 2 RFC will be considered for next release

* next-net-brcm
  - No patches in the backlog, fixes as they arrive

* next-net-intel
  - No update

* next-net-mlx
  - Fixes after this stage

* next-net-mrvl
  - CNXK net driver postponed to next release
  - No feature patches in backlog, only fixes


LTS
---

* `v19.11` (next version is `v19.11.9`)
  - Not much update at this stage

* `v20.11` (next version is `v20.11.2`)
  - "Xueming(Steven) Li" will help on `v20.11.2` release
  - email can be out this/next week


Defects
-------

* Quit for a while, there was good amount of activity after -rc1
* Some gcc11 build errors fixed but more still exist
  - Target is to fix all before -rc3
    ** Ferruh will follow next-net ones, ice & bnx2x


Opens
-----

* Regular Coverity checks continues, some fixes merged
  - Huawei sent lots of static analysis fixes in this release

* Cheng will follow security issues when he is back from holiday
  - We can try to align security fixes with LTS releases



.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>" for the invite.
*****

                 reply	other threads:[~2021-05-06 12:08 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=YJPcCpt6M4oS5uaL@silpixa00399752 \
    --to=ferruh.yigit@intel.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).