From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 13/05/2021
Date: Thu, 13 May 2021 13:25:58 +0100 [thread overview]
Message-ID: <YJ0a1rl2Uo1Wtvqt@silpixa00399752> (raw)
Release status meeting minutes {Date}
=====================================
:Date: 13 May 2021
:toc:
.Agenda:
* Release Dates
* -rc2/3 status
* Subtrees
* LTS
* Defects
* Opens
.Participants:
* Arm
* Debian/Microsoft
* Intel
* Individual contributor(s)
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.05` dates
- -rc3 is released on Wednesday, 12 May
** http://inbox.dpdk.org/dev/7142607.3L8AUzOtay@thomas/
- -rc4: Tuesday, 18 May
- Release: Friday, 21 May
* `v21.08` dates
- Proposal/V1: Wednesday, 2 June
- -rc1: Monday, 5 July
- Release: Tuesday, 3 August
* Please send roadmaps, preferably before beginning of the release
* Expecting a small `v21.08` release.
rc2/3 status
------------
* -rc2 test results
- Intel shared the -rc2 test results
** http://inbox.dpdk.org/dev/SJ0PR11MB5150E9B661923E5695B012A4FE539@SJ0PR11MB5150.namprd11.prod.outlook.com/
** Only one critical issue which already fixed
** Other found issues reported in Bugzilla
- IBM shared the -rc3 test result
** http://inbox.dpdk.org/dev/78b3dba4-c019-7bd0-023c-ce2713cb37f0@linux.vnet.ibm.com/
** Nothing critical
- Broadcom -rc2 tests all passed (reported offline)
* The -rc3 is new, no test reports yet.
- Initial Intel result shows no critical issues
** Intel plans to finish testing on next Tuesday
* Good to get more test results, please share the test reports
Subtrees
--------
* main
- Tooling and doc patches after this point
- There is Arm config patch in the backlog, Ruifeng will help on review
** The one from Huawei for SVE may be reviewed more
** Qualcomm one can be ready
- Dmitry's Windows patch can be postponed to next release
* next-net
- Will be a fixes after this point
- Some patches in the backlog not merged because of missing review and won't
be in the release, like bonding, memif, tap ...
- testpmd Windows patches postponed to next release
* next-crypto
- crypto unit test refactor patch merged
** There may be an issue reported by CI, it can be fixed separately
- mlx crypto PMD is postponed to next release
- NXP baseband driver is postponed to next release
* next-eventdev
- There is one fix for dlb2
* next-virtio
- Two fixes merged for -rc3, not more in the backlog
- A crash reported, need to fix it ASAP
** https://bugs.dpdk.org/show_bug.cgi?id=703
* next-net-brcm
- No patches in the backlog
* next-net-intel
- Will get fixes
* next-net-mlx
- 3 bugs found, will be fixes for them
* next-net-mrvl
- No patches in the backlog
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" requested support for backporting some commits
** http://inbox.dpdk.org/stable/28797869-b83a-fba8-5c85-8527e4107ac4@intel.com/T/#u
Defects
-------
* Ajit sent the report offline:
* gcc11 defects: 676, 673, 692, 690, 691
- Some fixed, some not reproduced anymore
- Only one we are aware of is in cryptodev test, Kevin sent a fix for it:
** https://patches.dpdk.org/project/dpdk/patch/20210505085314.54750-1-ktraynor@redhat.com/
* Bugs reported with 21.05 rc1/rc2: 693, 699, 688, 702, 687
- Since these are regressions, we should try and fix these in 21.05 - if
possible.
Opens
-----
* Nvidia is planning to upstream a GPU library for next release
- Can work together with any vendor willing to contribute, good to have a
vendor agnostic library
* 'next-net' sub-tree will be maintained by Andrew, Thomas & David during
'v21.08' (instead of Ferruh). Thanks for their support.
* Cheng started working on the security issues
* Alpine Linux has the target to run DPDK in a small container
- It uses musl libc and busybox
- Thomas is testing on Alpine
.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-13 12:26 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=YJ0a1rl2Uo1Wtvqt@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).