From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 4/03/2021
Date: Thu, 4 Mar 2021 11:55:27 +0000 [thread overview]
Message-ID: <YEDKrwqc/gfgm2Qv@silpixa00399752> (raw)
Release status meeting minutes {Date}
=====================================
:Date: 4 March 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* LTS
* Opens
.Participants:
* Arm
* Broadcom
* 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` and `Nvidia` for sending roadmap
Subtrees
--------
* main
- Some `eal` patches merged
- For Alibaba's PIO patchset better to do more test
** Ferruh will follow if Intel validation team can help
- ethdev SubFunction representor patches target next-net
- Will do an early pull from next-net
* next-net
- Progressing, backlog mostly consumed
** The ones not getting response won't be carried away to next release
- Not observed the peak for the release yet
* next-crypto
- One libcrypto patches, will commit today/tomorrow
- Rest are PMD/application patches
* next-eventdev
- There are three RFCs in the backlog
- octeontx2 changes from Marvell
- Intel DLB patchest
** Removing DLB v1 support
*** Why removing driver soon after it is merged
- Harry has SW eventdev patch
* next-virtio
- Will send roadmap
- Small patches in the backlog
- Two series remaining from the previous release
* next-net-brcm
- A big series is merged and waiting for pull
- No big series expected for release except regular fixes
* next-net-intel
- Progressing
- Some patches are missing in the tree will sync with Qi
* next-net-mlx
- Backlog is empty as of now, all merged
* next-net-mrvl
- A new octeontx3 driver expected for this release
LTS
---
* `v19.11.7-rc1` is out, please test
- http://inbox.dpdk.org/dev/20210222155851.3002880-1-christian.ehrhardt@canonical.com/
- Canonical, Red Hat reported test results
- Intel almost finished testing, 5 issues found, issues reported
** http://inbox.dpdk.org/dev/BY5PR11MB39733B6F1CD807F9377533F185979@BY5PR11MB3973.namprd11.prod.outlook.com/
*** Make build issue, devbind issue, rest are driver issues
* `v20.11.1-rc1` is out, please test
- http://inbox.dpdk.org/dev/20210222150918.279483-1-luca.boccassi@gmail.com/
- Canonical, Red Hat, Broadcom and Intel reported test results
- Intel reported some issues, working on them, not blocker for release
- Nvidia will send a report soon.
- Will OvS send a report?
* For both of them target release date is March 8.
- If no issues found during testing.
Opens
-----
* There are multiple ways to access old mails of mail list
- mail list archive: https://mails.dpdk.org/archives/dev/
** Archives can be downloaded and imported to mail list
*** At least `thunderbird` supports import
- public inbox: http://inbox.dpdk.org/dev/
** All mails can be viewed online
** Can download all mails as git repo
** Able to reply to specific email using `git send-email`
*** Web interface details on how to use
** Via Newsgroup server, details below
- From patchwork: https://patches.dpdk.org/project/dpdk/list/
** All patches/series can be viewed and downloaded from patchwork
* Access/reply all mail list emails via newsgroup server
- This is easy way to reply all emails not in your inbox
- Server is: `nntp://inbox.dpdk.org/inbox.dpdk.dev`
- At least `thunderbird` supports adding newsgroup accounts, but any `nntp`
client can be used
.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.
*****
TIP:: Try asciidoc for html output of the note
reply other threads:[~2021-03-04 11:55 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=YEDKrwqc/gfgm2Qv@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).