From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
by inbox.dpdk.org (Postfix) with ESMTP id 225C0A0562;
Thu, 4 Mar 2021 12:55:44 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id 9A14E40684;
Thu, 4 Mar 2021 12:55:43 +0100 (CET)
Received: from mga17.intel.com (mga17.intel.com [192.55.52.151])
by mails.dpdk.org (Postfix) with ESMTP id 6263D40147
for <dev@dpdk.org>; Thu, 4 Mar 2021 12:55:41 +0100 (CET)
IronPort-SDR: gst+42wjQwcjugOZK5m4NeTPQOERNde9te+At5HloM5ayEABN4/9HBxRDwnhXUhbA5pVuUZgJ8
tjiCCWCaCWVA==
X-IronPort-AV: E=McAfee;i="6000,8403,9912"; a="167298838"
X-IronPort-AV: E=Sophos;i="5.81,222,1610438400"; d="scan'208";a="167298838"
Received: from fmsmga008.fm.intel.com ([10.253.24.58])
by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
04 Mar 2021 03:55:39 -0800
IronPort-SDR: /Zw3dIZZ1CEVC9oOuXibyIU4J7glgdjN6/6WzW0+jCeGVFqYSrZk09MPx6oPl2m2XcflZDezB2
R0t86wxkv93w==
X-IronPort-AV: E=Sophos;i="5.81,222,1610438400"; d="scan'208";a="400576749"
Received: from silpixa00399752.ir.intel.com (HELO silpixa00399752)
([10.237.222.27])
by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
04 Mar 2021 03:55:38 -0800
Date: Thu, 4 Mar 2021 11:55:27 +0000
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Message-ID: <YEDKrwqc/gfgm2Qv@silpixa00399752>
Mail-Followup-To: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org,
Thomas Monjalon <thomas@monjalon.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Subject: [dpdk-dev] DPDK Release Status Meeting 4/03/2021
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
<mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
<mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>
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