From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 15/04/2021
Date: Thu, 15 Apr 2021 12:34:22 +0100	[thread overview]
Message-ID: <YHgkvidGdQtR5c49@silpixa00399752> (raw)
Release status meeting minutes {Date}
=====================================
:Date: 15 April 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* LTS
* Opens
.Participants:
* Arm
* Broadcom
* Canonical
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* OKTET Labs
* Red Hat
Release Dates
-------------
* `v21.05` dates
  - -rc1 pushed to  *Wednesday, 21 April*
  - -rc2:           Wednesday, 5 May
  - Release:        Friday, 14 May
* 1-5 May is Labor Day holiday in PRC.
Subtrees
--------
* main
  - ioat driver updates, may be postponed to -rc2
  - meson update
    ** Better to have in this release, but not urgent, can be postponed
  - Arm meson updates
    ** Bruce ack'ed the common code, Arm specific part needs ack
    ** There are config file changes, Hisilicon and CNXK depends on it
  - Reported a vhost TSO problem, work is going on
  - mbuf eCPRI will be reviewed, there is no enough review
  - Merged most of Thomas' series
  - Predictable RSS feature
    ** Comment on missing documentation and example
       *** Working on the documentation update
       *** Too short time for the example, it can be done gradually in next
	   release
  - FIB lookup method to l3fwd, can be merged today
  - Some fix patch can be merged after -rc1
* next-net
  - Not big backlog, ~50 patches, but there are multiple ethdev ones
    ** 4 ethdev flow API changes, reviews progressed but not finalised yet
       *** Relying Ori's review for them
       *** conntrack one has no review, it will be postponed if there is no
	   review before -rc1
    ** 1 ethdev meter API change, Cristian reviewed, new version expected
    ** 2 other ethdev changes, queue state and sanity checks ones
       *** New version received for queue state one, can be merged soon
           **** There is a testpmd patch depends on this
       *** Andrew reviewed sanity checks one, minor change request
	   **** It does not look critical for the release but prefer to get it
		if it is ready
  - new PMD `ngbe` form Wangxun, new version requested
  - pulled from vendor trees yesterday
  - There are testpmd multi-process and Windows enablement patches
    ** For multi-process one waiting for new version because of minor issues
       *** There is a long term testing concern, should DTS updated to verify
	   testpmd multi-process support?
    ** Windows enablement patch can be postponed to next release
* next-crypto
  - 2/3 patches from mlx, will apply soon
  - Ciara's patch can be merged later
  - "raw data path dequeue API" by Fan waiting for reply
  - Two PMDs for -rc2
    ** mlx5 crypto PMD
    ** NXP baseband PMD
  - "lookaside IPsec UDP encapsulation and transport mode" patch
    ** Can Konstantin ack again, if so can go into -rc1
* next-eventdev
  - Intel dlb2, reviews going on
    ** Rename to dlb2 -> dlb is ABI break, needs approval
       *** Also this may cause issue on LTS, dlb in LTS will be different than
	   dlb in latest release
       *** May hold rename until next LTS
  - Marvell CNXK postponed to -rc2
    ** Because of common code dependency
  - "eventdev crypto adapter" support, Abhinandan is reviewing
    ** There is an ABI discussion going on
* next-virtio
  - There is a hotfix for -rc1, a trivial issue
    ** Will go in directly to next-net
  - Remaining patches will be considered for -rc2
  - A vdpa patch rejected while pulling to main repo, since it breaks the build
    for Alpine Linux
    ** Need to communicate with Matan for it
* next-net-brcm
  - 2/3 fixes to send, but they are not critical, may wait -rc2
* next-net-intel
  - Progressing
* next-net-mlx
  - Progressing
* next-net-mrvl
  - CNXK net driver review is going on, may go into -rc2
LTS
---
* `v19.11.8-rc1` is out, please test
  - http://inbox.dpdk.org/dev/20210409074357.2499008-1-christian.ehrhardt@canonical.com/
  - The -rc is specifically to address meson build error
* `v20.11` (next version is `v20.11.2`)
  - Not much update at this stage
Opens
-----
* Alpine Linux and musl libc should be tested by maintainers
  - We should add this to the CI but it is not there yet
* Latest DPDK fails to build on Fedora 34 (which will be released soon)
  - Kevin submitted Bugzilla defects for it
  - Possibly because of new gcc version
  - It is good idea to test with Fedora Rawhide
* fast test suit is failing for PPC without root access
  - There is a patch to fix it but there is no review
* There is a new security team member, working on security issues can continue
  after he ramped up
* Regular coverity scans are going on, and there are some coverity fixes
  already hit the mail list, please review/merge them
.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-15 11:34 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=YHgkvidGdQtR5c49@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).