[dpdk-dev] DPDK Release Status Meeting 4/02/2021

[dpdk-dev] DPDK Release Status Meeting 4/02/2021

[Ferruh Yigit]

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 <john.mcnamara@intel.com>" for the invite.