[dpdk-dev] DPDK Release Status Meeting 7/05/2020

[dpdk-dev] DPDK Release Status Meeting 7/05/2020

[Ferruh Yigit]

Minutes 7 May 2020
------------------

Agenda:
* Release Dates
* -rc1 status
* Subtrees

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


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

* v20.05 dates:
  * -rc2 pushed to		*Monday 11 May 2020*
  * -rc3			Friday 18 May 2020
  * Release pushed to		*Friday 22 May 2020*

* v20.08 proposal dates, please comment:
  * Proposal/V1:		Tuesday, 16 June 2020
  * Integration/Merge/RC1:	Tuesday, 14 July 2020
  * Release:			Friday, 7 August 2020

  * Please send roadmap for the release


-rc1 status
-----------

* No major/critical issue reported

* Intel testing found some issues and tracing them, there are still some open
  defects


Subtrees
--------

* main
  * vfio-pci VF token patchset may be pushed next release, it is not ready yet
    * thanks to Haiyue Wang for his effort (also for his __rte_internal work)
  * __rte_internal patcheset merged
    * In next stage drivers in common folder need to mark their APIs
      * NXP already sent patch for it
      * Do we need patches for QAT too?
  * gcc10 fixes
    * There are still warnings
      * mbuf markers and -fno-common remaining, not easy to address
    * We can ignore remaining ones in -rc2 while working for proper fixes
      * Need to mark/comment ignore to not forgot it
  * rte_graph has been merged
  * Will review telemetry patches today

* next-net
  * bonding patches in backlog, we need help on reviewing bonding patches
  * ethdev unknown speed change can be postponed to next release, there are
    some unresolved comments in mail list
  * There is a dpaa/dpaa2 patchset waiting for new version
  * Some bnxt patches not pulled, waiting for change
  * ~50 patches at this stage, not all will make -rc2
  * Raslan reported a tap PMD build error, will check offline

* next-crypto
  * A little later for -rc2, will be ready for pull on Monday
  * chacha20-poly1305 patchset is library change but can be considered for -rc2
    if the ABI versioning implementation is good

* next-eventdev
  * Nothing for -rc2, there may be some patches for -rc3

* next-virtio
  * 8 patches in the queue
  * There is an OvS issue but fix requires DPDK ABI break, that is why
    DPDK side fix will wait and need to find another solution on OvS side

* next-net-intel
  * Some fixes for -rc2 has been merged and pulled to next-net
  * fm10k patches are not received yet, if they are not received timely before
    -rc2, it may miss the release.

* next-net-mlx
  * There will be some more patches for -rc2
  * Can rte flow test application merged for -rc2?

* next-net-mrvl
  * There are a few patches in backlog



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.