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 F16D1A0524; Thu, 4 Feb 2021 13:06:28 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 89E9E240632; Thu, 4 Feb 2021 13:06:28 +0100 (CET) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mails.dpdk.org (Postfix) with ESMTP id BC104240623 for ; Thu, 4 Feb 2021 13:06:26 +0100 (CET) IronPort-SDR: nXmo4U9cnSqZ209Mcq5z9musmH9icJlLlTbRzkaOdeY70ilxqz6aP1lBp6lxPjdQS8RtF0yGna oG4DTTBrTEdA== X-IronPort-AV: E=McAfee;i="6000,8403,9884"; a="177720430" X-IronPort-AV: E=Sophos;i="5.79,400,1602572400"; d="scan'208";a="177720430" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Feb 2021 04:06:25 -0800 IronPort-SDR: e3PjDf2FFhUXTcEKzsMnwarYvghJ53DraxyIMXEPIMc4Da0QzVDyUjXd2laQYN1CNXDH4I7Z9L /Ka+BmeITF9A== X-IronPort-AV: E=Sophos;i="5.79,400,1602572400"; d="scan'208";a="393132158" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.211.210]) ([10.213.211.210]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Feb 2021 04:06:24 -0800 From: Ferruh Yigit To: "dev@dpdk.org" Cc: Thomas Monjalon Message-ID: Date: Thu, 4 Feb 2021 12:06:20 +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 4/02/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" Meeting minutes of 4 February 2021 ---------------------------------- Agenda: * Release Dates * -rc2 status * Subtrees * LTS * Bugzilla * Opens Participants: * Arm * Broadcom * Debian/Microsoft * Intel * Marvell * Nvidia * NXP * Red Hat Release Dates ------------- * v21.02 dates * -rc2 is released on Friday, 29 January 2021 * http://inbox.dpdk.org/dev/2701263.OCiMXv1sLx@thomas/ * -rc3: Thursday, 4 February 2021 * Release: Friday, 12 February 2021 * v21.05 draft dates, please comment: * Proposal/V1: Thursday, 18 March * -rc1: Thursday, 15 April * Release: Friday, 14 May * Reminder of roadmaps for 21.05. -rc2 status ----------- * Intel sent test results, 90% validation completed, no critical issue: * http://inbox.dpdk.org/dev/da5b7eb7ec9c40a999a2cf6edde15001@intel.com/ Subtrees -------- * main * Not much patches in the backlog * Some doc and example patches * There are a few little fixes can wait next release * next-net * Target is to close the tree for -rc3 today * A new hns3 set is in the queue * Will pull from intel, mlx & mrv trees today * pcap fixes can go in if tested on time * nxp & txgbe series new version not received yet, they will miss the -rc3, and postponed to next release * next-crypto * A few patches are in backlog for -rc3 * doc, test crypto & a PMD patches * Planning to merge them today * next-eventdev * Patches will be merged today * One of them is for the coverity fixes * next-virtio * Two fixes merged * Should be good for the release * Only one remaining patch, can wait next release * next-net-mlx * Some patches merged for -rc3, waiting pull * There can be more fixes, all will be ready today * next-net-brcm * -rc2 testing looks good * No more patch expected for -rc3 * next-net-intel * Some patches merged for -rc3, waiting pull * next-net-mrvl * there will be one/two more patches for -rc3 LTS --- * v19.11.7 * Christian Ehrhardt started working on it. * v20.11.x * Luca will work on it. Bugzilla -------- * Ajit mentioned there is more activity these days * Some old defects are still open and needs attention * Thomas has a script to close Bugzilla automatically when patches merged into the main tree. But this requires "Bugzilla ID:" tag provided in commit log, please provide the tag always when the commit is to solve a Bugzilla defect, more detail is on documentation: * doc.dpdk.org/guides/contributing/patches.html#patch-fix-related-issues * Also should wait patches to be merged into main repo before closing defects. Opens ----- * There is still problem in Coverity that prevents assigning defects, John is following the issue, it should be fixed soon in the coverity end. * Ferruh is running cppcheck time to time, better to upstream a script for it. * There are other static analysis checkers we can try them too, like clang-analyzer or gcc-analyzer. * https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Static-Analyzer-Options.html * Also John is checking lgtm.org time to time, it has good interface but not allows to mark false positives etc. * https://lgtm.com/projects/g/DPDK/dpdk/?mode=list * It may be possible to assign some intern for the static analysis tasks, or we can consider benefiting from Google Summer of Code for it * https://summerofcode.withgoogle.com/ * pmdinfogen updated with new ptyhon re-write, so the 'GPL-2.0' license exception because of the old version can be removed now. 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.