From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 604ADA09F6; Thu, 17 Dec 2020 12:36:57 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 54257CA12; Thu, 17 Dec 2020 12:36:55 +0100 (CET) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 3A491CA08 for ; Thu, 17 Dec 2020 12:36:53 +0100 (CET) IronPort-SDR: YHvK+OKk7R7kJ3bbYFaZd+N3Bp6+AoQmTnQbxlGLNRyw809pZ9xetoVZobNw4+ng7BBlogEhoc 5FLpBb69IDIQ== X-IronPort-AV: E=McAfee;i="6000,8403,9837"; a="172666165" X-IronPort-AV: E=Sophos;i="5.78,426,1599548400"; d="scan'208";a="172666165" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Dec 2020 03:36:51 -0800 IronPort-SDR: gBiIAiwuxqFYKlRoh7ajCMCTlYb/FF1gdqAtIO2Lys2MlNw/s5aTfcNVI6E1iTj+eSgLd0FBi7 1K3MuMHcLB+w== X-IronPort-AV: E=Sophos;i="5.78,426,1599548400"; d="scan'208";a="369798482" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.233.164]) ([10.213.233.164]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Dec 2020 03:36:50 -0800 From: Ferruh Yigit To: "dev@dpdk.org" Cc: Thomas Monjalon Message-ID: <079b2070-296a-0b1d-3ba6-d0ec2ae4e359@intel.com> Date: Thu, 17 Dec 2020 11:36:46 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] DPDK Release Status Meeting 17/12/2020 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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" Meeting minutes of 17 December 2020 ----------------------------------- Agenda: * Release Dates * Highlights * Subtrees * LTS * OvS * Opens Participants: * Arm * Broadcom * Debian/Microsoft * Intel * Marvell * Nvidia * NXP * Red Hat Release Dates ------------- * v21.02 dates * Proposal/V1: Sunday, 20 December 2020 * -rc1: Friday, 15 January 2021 * Release: Friday, 5 February 2021 * Please send roadmaps, preferably before beginning of the release * Thanks to NTT, Huawei hns3, Intel, Red Hat, Marvell, Broadcom for sending roadmap Highlights ---------- * Next two meetings will be cancelled due to holidays. Happy holidays all. Subtrees -------- * main * Nothing major at this stage * Tools patches and several windows patches * next-net * Not high volume, some patches reviewed/merged * Bonding patch cleanup with help of Connor * What is the status of the Intel packet mirror patch? * next-crypto * Not too many patches in this release, there are two sets in the backlog * app: add multi process crypto application * This was good to test some APIs * Patch from previous release, not updated * compress PMD from mlx5 * enqueue & dequeue callbacks * from previous release * There were some warnings, new version expected * next-eventdev * No patches in the backlog * There is DLB consolidation in the roadmap, waiting for it * next-virtio * Small series only, no big backlog * Working on virtio rework * next-net-mlx * Some sets sent, waiting for more * next-net-brcm * A few patches in the backlog and expecting a few more * next-net-intel * Some big sets in the backlog, a few small ones merged * next-net-mrvl * There are armada patches, will be reviewed * meson musdk pkg-config update will go in to next-net LTS --- * v19.11.6-rc1 is out, please test * http://inbox.dpdk.org/dev/20201203093856.299103-1-luca.boccassi@gmail.com/ * Waiting for test reports, some already received * There are some regression reported by Intel, and suggested fix is causing regression * Release was planned for today but it is postponed one day while waiting update on above issues * v18.11.11 work is going on * waiting for backports, request emails sent * Good response from accumulated waiting patches for backport * Planning to release the -rc today OvS --- * DPDK v20.11 is integrated for the coming 2.15 release Opens ----- * Asaf shared a draft release process documentation * Not ready yet for sending as patch * Security (CVE) process * There is an effort in Intel to find more resources for it * Inactive maintainers * There are some names listed in the maintainers file but they are not active anymore, removing their name can help filling those positions. * What is the time taken as inactive? * No interaction in the mail list for 3 releases? * If missing response is blocking a component, it can be taken as inactive without waiting 3 releases. * It is hard to fill a maintainer position if it is for a vendor driver * Should common code and vendor PMDs be treated differently on this? * Should we mark PMDs without active maintainer as 'unmaintained'? 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.