From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 25/03/2021
Date: Thu, 25 Mar 2021 13:20:13 +0000 [thread overview]
Message-ID: <YFyODXlKB0Kr0za3@silpixa00399752> (raw)
Release status meeting minutes {Date}
=====================================
:Date: 25 March 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* LTS
* Conferences
* Opens
.Participants:
* Arm
* Canonical
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.05` dates
- Proposal/V1 passed, it was on Thursday, 18 March
- -rc1: Thursday, 15 April
- Release: Friday, 14 May
* Please send roadmaps, preferably before beginning of the release
- Thanks to `Marvell`, `Huawei hns3`, `Nvidia`, `Wangxun`, `Intel` and `Arm`
for sending roadmap
Subtrees
--------
* main
- eal patches are under review
** there are many eal patches
- Dmitry reported regression on Windows related memory subsystem
** Need Anatoly's support
- pipeline patches are merged
* next-net
- Progressing, nothing critical, ~80 patches in backlog
- ethdev library changes planned to be merged before -rc1
** expected peak of patches not observed, more driver patches still may
arrive
- pulled from vendor trees yesterday
* next-crypto
- Some patches are merged, nothing critical
- ipsec gateway discussions/reviews are going on
- test/application patches are remaining
* next-eventdev
- "periodic mode for event timer adapter" is merged
- Will be sending new version for Marvell CNXK
** Because of common code dependency it may be postponed to -rc2
- Intel dlb1 remove set merged
- Intel dlb2, new version expected
* next-virtio
- Chenbo is preparing a pull request
- Half of the patches in the backlog reviewed
- There is an RFC from Ilya to use SocketPair Broker to improve vhost in
containers
** It is under review, may be late for 21.05
** It has a dependency external library by Ilya
* next-net-brcm
- Progressing
* next-net-intel
- Progressing
* next-net-mlx
- Progressing, nothing critical
- More patches are due, 1-2 new features are expected
* next-net-mrvl
- Progressing
- Waiting new version of qede patch from Red Hat
LTS
---
* `v19.11.7` is released
- http://inbox.dpdk.org/dev/20210317170343.3267049-1-christian.ehrhardt@canonical.com/
- A regression is reported with 19.11.7
** An 19.11.8-rc will be created, based on interest from stakeholders, and
test reports received, and early 19.11.8 can be released.
If there is no enough interest fix will wait regular 19.11.8 cycle
* `v20.11.1` is released
- http://inbox.dpdk.org/dev/20210308181351.409609-1-luca.boccassi@gmail.com/
Conferences
-----------
* DPDK APAC 2021 event was on 22-23 March, presentations can be found at:
- https://events.linuxfoundation.org/dpdk-summit-apac/program/schedule/
Opens
-----
* Security issues
- The resourcing discussed in the governing board, the role requires a trusted
name but chain of trust can be accepted.
** Can discuss the possible candidate(s) again in next techboard meeting
** It will be good to have an assigned resource for security issues
- Why most of the issues are in vhost/virtio domain?
** vhost is the interface to untrusted domain
** vhost is easier to test by security researchers, it doesn't require any
specific hardware
.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-03-25 13:20 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=YFyODXlKB0Kr0za3@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).