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 22/04/2021
Date: Thu, 22 Apr 2021 15:50:41 +0100	[thread overview]
Message-ID: <YIGNQarMJp69MeMg@silpixa00399752> (raw)

Release status meeting minutes {Date}
=====================================
:Date: 22 April 2021
:toc:

.Agenda:
* Release Dates
* -rc1 status
* Subtrees
* LTS
* Opens

.Participants:
* Arm
* Broadcom
* Debian/Microsoft
* Intel
* Individual contributor(s)
* Marvell
* Nvidia
* Red Hat


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

* `v21.05` dates
  - -rc1 is released on Wednesday, 21 April
    ** http://inbox.dpdk.org/dev/4984397.K2Fab8RJsf@thomas/
  - -rc2:           Wednesday, 5 May
  - Release:        Friday, 14 May

* 1-5 May is Labor Day holiday in PRC.


rc1 status
----------

* -rc1 released yesterday, not enough testing done yet

* Initial Intel testing did not found any major or blocking issue


Subtrees
--------

* main
  - mbuf eCPRI there is no enough review
    ** will miss this release
  - ioat driver updates, postponed to -rc2
  - There is Windows build issue, will fix it
  - Will improve log registration
    ** Some work already done/merge, will try to add more in this release
  - There is a patch that batch renamed some folders
    ** https://git.dpdk.org/dpdk/commit/?id=99a2dd955fba
    ** Please be aware of the change, this will break some git blame output
  - The indentation of meson files changed
    ** https://git.dpdk.org/dpdk/commit/?id=6fc406593ac1
    ** Maintainers should be careful on this change

* next-net
  - majority of the ethdev patches are merged
    ** the mutex update for the multi-process left, discussions going on
    ** testpmd multi-process patch not merged, may be postponed to next release
  - driver/testpmd patches and fixes for -rc2

* next-crypto
  - Ciara's patch can waiting for new version
  - Two PMDs for -rc2
    ** mlx5 crypto PMD
    ** NXP baseband PMD

* next-eventdev
  - Patches merged for -rc1, dlb and CNXK eventdev driver for -rc2
  - For dlb2, waiting for techboard decision on rename

* next-virtio
  - Remaining patches will be considered for -rc2

* next-net-brcm
  - Majority of the patches made the -rc1, not much for -rc2

* next-net-intel
  - A base code updated expected for -rc2
  - There are more fixes and driver updated in the backlog

* next-net-mlx
  - All planned features are merged for -rc1
  - There will be some more features for -rc2
    ** Some are already in the mail list

* next-net-mrvl
  - CNXK net driver will be merged on -rc2


LTS
---

* `v19.11.8` is released
  - http://inbox.dpdk.org/dev/20210416094441.1315964-1-christian.ehrhardt@canonical.com/

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


Opens
-----

* There is a better to way to include the code into documentation
  - https://patches.dpdk.org/project/dpdk/patch/20210421091146.1384708-1-conor.walsh@intel.com/
  - We should use this method instead of copy/paste code into doc
  - It would be nice to have a generic cleanup on existing documentation

* There are some new Bugzilla defect for build issues
  - Kevin submitted Bugzilla defects for it
  - Reproduces on Fedora 34 (which will be released soon)
  - Wide range of compiler versions are supported
    ** Because large variety of OS versions are supported

* There is a new security team member, working on security issues can continue
  after he ramped up



.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-04-22 14:50 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=YIGNQarMJp69MeMg@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).