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 71B8FA0548; Thu, 1 Apr 2021 12:43:49 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 59FB2141044; Thu, 1 Apr 2021 12:43:49 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id C3A374067B for ; Thu, 1 Apr 2021 12:43:47 +0200 (CEST) IronPort-SDR: /5CSQAPjCbgeg6JWVQwyYLLbZmxHNGtaDYVu2ATuKFViylyjiD52JdlvCq00GfrYhB0G6iqdxh 1/cEHUjK77XQ== X-IronPort-AV: E=McAfee;i="6000,8403,9940"; a="192242500" X-IronPort-AV: E=Sophos;i="5.81,296,1610438400"; d="scan'208";a="192242500" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Apr 2021 03:43:46 -0700 IronPort-SDR: mQ1sbMJhC8u9L1XXy1a9A9ALJ63yC758S7mPSHCe45H4uZVSUdANqZccOkAA/VMhPWBpGPeGGW JJxO/pjpK/7Q== X-IronPort-AV: E=Sophos;i="5.81,296,1610438400"; d="scan'208";a="610875804" Received: from silpixa00399752.ir.intel.com (HELO silpixa00399752) ([10.237.222.27]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Apr 2021 03:43:44 -0700 Date: Thu, 1 Apr 2021 11:43:37 +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 01/04/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: 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 " for the invite. *****