[dpdk-dev] DPDK Release Status Meeting 12/03/2020

[Ferruh Yigit <ferruh.yigit@intel.com>]

Minutes 12 March 2020
---------------------

Agenda:
* Release Dates
* Subtrees
* OvS
* Opens

Participants:
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* Red Hat


Release Dates
-------------

* v20.05 dates:
  * Proposal/V1:		Wednesday 18 March 2020
  * Integration/Merge/RC1:	Friday 17 April 2020
  * Release:			Wednesday 20 May 2020

  * Marvell & Arm already sent roadmap for 20.05, all vendors please share the
    roadmap for the release.


Subtrees
--------

* main
  * Working on some eal patches, will merge some patches today/tomorrow
  * Working on Windows patches
  * Running coverity on travis has some challenges, Thomas will debug it more
  * There can be an merge from sub-trees, next-net will clarify status before it

* next-net
  * It is progressing, some patches already merged
  * Not much improvement on ethdev RFCs, would like to resolve them before
    it gets busy for the release cycle
  * There is a new Intel PMD, igc

* next-crypto
  * No update in the tree

* next-eventdev
  * There is one patchset waiting that will be merged soon

* next-virtio
  * Not much update, there are some virtio driver patches
  * There are some example rework to use vhost PMD
    * This is to be able to test vhost PMD more extensively within DPDK

* next-net-intel
  * Multiple shared code drops sent
  * Some patches already merged and pulled

* LTS

  * 18.11.7
    * Majority of the backports done
    * -rc1 expected towards end of next week
    * Release planned for mid April

  * 19.11.1-rc1 released, please test and report results
    * https://mails.dpdk.org/archives/dev/2020-March/158923.html
    * Received test reports and some additional patches merged to fix reported
      issues
    * Ian will send OvS test result too, will wait it
    * Can have an -rc2 afterwards
    * Will release on Monday 16th, as planned


OvS
---

* Removed pdump functionality, not used much by community
* vhost TSO updates may have broken the zero copy support, investigating
* Both above features are experimental


Opens
-----

* Affect of coronavirus, should something done to mitigate the risk
  * Should we add backup maintainers for all sub-trees?
    * The ones missing backup maintainer:
      next-crypto
      next-eventdev
      Most of the vendor sub-trees under next-net, except Intel
    * It looks like we can cover possible missing maintainers organically
  * Possible work from home conditions seems won't affect much, working from
    home works for many parties.



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 Thursdays at 8:30 UTC. If you wish to attend just
send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.