From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 11/03/2021
Date: Thu, 11 Mar 2021 14:34:23 +0000 [thread overview]
Message-ID: <YEoqXRFaAiUHgzrK@silpixa00399752> (raw)
Release status meeting minutes {Date}
=====================================
:Date: 11 March 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* LTS
* Conferences
* Opens
.Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.05` dates
- Proposal/V1: 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` and `Intel` for
sending roadmap
Subtrees
--------
* main
- For Alibaba's PIO patchset better to do more test
** Intel verification looks good
- Thomas is doing some clean up patches, more to come
- Will do an early pull from next-net
* next-net
- Progressing, nothing critical
- Not observed the peak for the release yet
- Pulled from vendor sub-trees
** waiting brcm tree for small changes
** Pulling from sub-trees less frequently, to reduce the overhead
Planning to have weekly pulls, on Wednesdays
- There is a new set of octeontx3 drivers, net driver with common
driver dependency
** New drivers will go from mrvl tree to main repo directly
*** Jerin will manage branches, one for to be pulled from main repo
other is to be pulled from next-net
* next-crypto
- Not much update
- Will review/merge some apps and drivers this week
* next-eventdev
- Some patches merged, some more to go
- Will prepare a pull request when all merged
* next-virtio
- Two series remaining from the previous release
- Two new feature added to backlog for this release
* next-net-brcm
- Waiting update for existing set
* next-net-intel
- Some base file updates and raw/ifpga merged
- More in the backlog
* next-net-mlx
- A fix in the tree pulled to next-net
- More patches expected before v1 deadline
* next-net-mrvl
- A few patches merged and pulled by next-net
LTS
---
* `v19.11.7-rc2` is out, please test
- http://inbox.dpdk.org/dev/20210310133709.562846-1-christian.ehrhardt@canonical.com/
- Intel reported and fixed some issues, -rc2 released with fixes
- New planned release date is March 17
* `v20.11.1` is released
- http://inbox.dpdk.org/dev/20210308181351.409609-1-luca.boccassi@gmail.com/
Conferences
-----------
* DPDK APAC 2021 event is approaching, it is on 22-23 March
- https://www.dpdk.org/event/dpdk-summit-apac-2021/
- https://events.linuxfoundation.org/dpdk-summit-apac/
Opens
-----
* John is evaluating lgtm.com
- https://lgtm.com/projects/g/DPDK/dpdk/?mode=list
* Is there anyone did code review on github, please reach out for BKMs or for
experience sharing
.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-11 14: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=YEoqXRFaAiUHgzrK@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).