[dpdk-dev] DPDK Release Status Meeting 20/12/2018

[Ferruh Yigit]

Minutes 20 December 2018
------------------------

Agenda:
* Release Dates
* RC1 deadline
* Subtrees
* OvS
* Opens


Participants:
* Debian
* Intel
* Mellanox
* RedHat


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

* v19.02 dates:
  * First release candidate: December 21, 2018
  * Last release candidate: January 25, 2019
  * Release: February 1, 2019

* Roadmap page: http://core.dpdk.org/roadmap/#dates


RC1 deadline
------------

* First release candidate is this Friday (tomorrow)!
* It will be a hard deadline
* Power library will send a new version to fix meson build
* ipsec library, there are comments to be addressed, test team is ready
  to test it in the RC1 scope
* Qian expressed she prefers a more complete RC1 rather than pushing some
  features to next RC
* There is no feature planned to be pushed to RC2
* Pablo is back from holiday! (Welcome)


Subtrees
--------

* main
  * Pulled from sub-trees, next-net, next-crypto, next-eventdev
  * Merging patches, rapid response in mail list helps.

* next-net
  * Will be ready for pull on Friday
  * Pulled from next-net-intel & next-net-mlx

* next-virtio
  * Will be more patches on Thursday or Friday

* next-crypto
* next-eventdev
* next-pipeline
* next-qos
  * No update, we need attendance from maintainers

* Stable trees
  * v16.11.9-rc1 is ready, ATT test result is good, Intel test team assessing
    test plas
  * Kevin will prepare an RC1 for 18.08.1 soon/today


OvS
---

* v18.11 merged to OvS master, mostly OK except a few minor fix


Opens
-----

* Coverity
  * Coverity is partially back, but builds still put into queue and moves slow
  * techboard has been discussed about tooling


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 at intel.com>" for the invite.