From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 01/04/2021
Date: Thu, 1 Apr 2021 11:43:37 +0100 [thread overview]
Message-ID: <YGWjys9qroHa6zUJ@silpixa00399752> (raw)
Release status meeting minutes {Date}
=====================================
:Date: 01 April 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* LTS
.Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.05` dates
- -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
- merging next-net today
- Windows memory regression fix merged
- Locking review on thread patch by Microsoft
- Reported a vhost TSO problem
** Patches sent to mail list
*** But fix may break compatibility with old versions
* next-net
- Progressing, nothing critical, ~80 patches in backlog
- ethdev library changes planned to be merged before -rc1
- new PMD `ngbe` form Wangxun
** Also there is octeontx3 but that will go directly to main repo
- Xiaoyun is reviewing the testpmd patches
- pulled from vendor trees yesterday
* next-crypto
- Some patches are merged, nothing critical
- Will merge more patches on weekend
- mlx crypto PMD still in RFC state
** may not be an update on it this release
* next-eventdev
- "periodic mode for event timer adapter" is merged
- Intel dlb2 sent two days ago
** Will try to review this week
** And will try to close it for -rc1 if not -rc2
- Marvell CNXK may be postponed to -rc2
** Because of common code dependency
- Two more features in the queue
** "event vectorization" support
*** Reviewed, will be merged today/tomorrow
** "eventdev crypto adapter" support
*** Abhinandan will review
* next-virtio
- Quite some patches are merged by Chenbo and pull request sent
- Planning to have one more pull request before -rc1
* next-net-brcm
- No new patches for now, may have some fixes
* next-net-intel
- Progressing
* next-net-mlx
- ~30 patches on queue, progressing
* next-net-mrvl
- a `qede` patch is waiting for release notes update
- octeontx3 net driver may be pushed to -rc2
** because of the common code dependency which may be merged for -rc1
LTS
---
* `v19.11` (next version is `v19.11.8`)
- Waiting OvS test result to decide an out of cycle `19.11.8-rc` or not
* `v20.11` (next version is `v20.11.2`)
- Not much update at this stage
.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-01 10:43 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=YGWjys9qroHa6zUJ@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).