From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3D26DA0524; Thu, 6 May 2021 14:08:05 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9D328410DB; Thu, 6 May 2021 14:08:04 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mails.dpdk.org (Postfix) with ESMTP id 3483B40040 for ; Thu, 6 May 2021 14:08:02 +0200 (CEST) IronPort-SDR: qYSNXfGHwSrIlptHHQ0u/UeDq+uTiJejbeyhRkGX22zYx5hdTIPbnx8MMdmqMr8QNM7Az0TSjx 8Iv4WFTl0m1A== X-IronPort-AV: E=McAfee;i="6200,9189,9975"; a="219333997" X-IronPort-AV: E=Sophos;i="5.82,277,1613462400"; d="scan'208";a="219333997" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 May 2021 05:08:01 -0700 IronPort-SDR: iLUcM6o1tQhlQxSb5i3yKXO29qJGlOyH2a8qlmwoNTHSskinRHJFMvAwcLyuyIya82LxdYBAPJ wQVzmhmRY6qg== X-IronPort-AV: E=Sophos;i="5.82,277,1613462400"; d="scan'208";a="469427555" Received: from silpixa00399752.ir.intel.com (HELO silpixa00399752) ([10.237.222.27]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 May 2021 05:08:00 -0700 Date: Thu, 6 May 2021 13:07:53 +0100 From: Ferruh Yigit To: dev@dpdk.org Cc: Thomas Monjalon Message-ID: Mail-Followup-To: Ferruh Yigit , dev@dpdk.org, Thomas Monjalon MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Subject: [dpdk-dev] DPDK Release Status Meeting 06/05/2021 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Release status meeting minutes {Date} ===================================== :Date: 6 May 2021 :toc: .Agenda: * Release Dates * -rc2 status * Subtrees * LTS * Defects * Opens .Participants: * Arm * Broadcom * Debian/Microsoft * Intel * Marvell * Nvidia * Red Hat Release Dates ------------- * `v21.05` dates - -rc2 is released on Wednesday, 5 May ** http://inbox.dpdk.org/dev/3585896.ctXz43JjJv@thomas/ - -rc3: Wednesday, 12 May - -rc4: Tuesday, 18 May - Release: Friday, 21 May * `v21.08` draft dates (updated), please comment: - Proposal/V1: Wednesday, 2 June - -rc1: Monday, 5 July - Release: Tuesday, 3 August * Expecting a small `v21.08` release. rc2 status ---------- * The -rc2 is so new, no test reports yet. * Good to get more test results, please share the test reports Subtrees -------- * main - example, tooling and fix patches in the backlog - i40e/iavf PF reset issue adding new bus/pci API, it may be later for this release ** Is the fix critical for this release? * next-net - 'ena' PMD base code update and fix patches are in backlog * next-crypto - All merged except mlx crypto PMD and crypto unit test refactor ** mlx crypto PMD, will review it today and merge it for -rc3 if all good ** crypto unit test refactor is causing segfault *** Working on it - NXP baseband driver is postponed to next release - Fixes will be merged for -rc3 * next-eventdev - Fixes as they arrive * next-virtio - Backlog is clean, 2 RFC will be considered for next release * next-net-brcm - No patches in the backlog, fixes as they arrive * next-net-intel - No update * next-net-mlx - Fixes after this stage * next-net-mrvl - CNXK net driver postponed to next release - No feature patches in backlog, only fixes LTS --- * `v19.11` (next version is `v19.11.9`) - Not much update at this stage * `v20.11` (next version is `v20.11.2`) - "Xueming(Steven) Li" will help on `v20.11.2` release - email can be out this/next week Defects ------- * Quit for a while, there was good amount of activity after -rc1 * Some gcc11 build errors fixed but more still exist - Target is to fix all before -rc3 ** Ferruh will follow next-net ones, ice & bnx2x Opens ----- * Regular Coverity checks continues, some fixes merged - Huawei sent lots of static analysis fixes in this release * Cheng will follow security issues when he is back from holiday - We can try to align security fixes with LTS releases .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 " for the invite. *****