DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] DPDK Release Status Meeting 4/7/2019
@ 2019-07-04 10:11 Ferruh Yigit
  0 siblings, 0 replies; only message in thread
From: Ferruh Yigit @ 2019-07-04 10:11 UTC (permalink / raw)
  To: dpdk-dev
  Cc: John McNamara, Stokes, Ian, Thomas Monjalon, Jerin Jacob, Akhil,
	Goyal, Cristian Dumitrescu, Qian Xu, Yongseok Koh,
	Maxime Coquelin, Qi Zhang, Shahaf Shuler, Pablo de Lara

Minutes 4 July 2019
-------------------

Agenda:
* Release Dates
* Subtrees
* OvS
* Opens


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


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

* v19.08 dates:
  * RC1 	Monday 08 July
  * RC2		Friday 19 July
  * Release	Thurs  01 August

* v19.11 dates:
  * Proposal/V1               Friday 06 September 2019
  * Integration/Merge/RC1     Friday 11 October   2019
  * Release                   Friday 08 November  2019


Subtrees
--------

* main
  * There are some patches already waiting
  * documentation/tooling/unit test patches will be considered for rc2
  * Some patchset are missing review, some stuck on questions
  * mcslock patchset will be considered for rc2 because of missing review

* next-net
  * There are more ethdev and PMD patches, new octeontx2 PMD is waiting
  * Will try to get library changes to rc1, pmd ones will remain for rc2
  * Ferruh will be off on Friday

* next-virtio
  * A patch is candidate for rc1
  * Tiwei will cover Maxime for Friday

* next-net-mrvl
  * octeontx2 PMD merged, tree is ready for pull

* next-net-mlx
  * Need to do the maintainer handover officially

* next-crypto
  * waiting patchses cryptodev, bbdev, test_compress
  * For bbdev, waiting for automated build results
  * ipsec patchset will be considered for rc2

* next-eventdev
  * Tree pulled
  * New patches can be pushed to rc2

* Stable trees
  * No update


OvS
---

* 2.12 branch will be created soon


Opens
-----

* There is exiting build error in main repo, Marvel sent the fix

* Patchwork shows build failure for most of the patches, can it be possible to
trigger them manually to try again?
  * Build can be triggered manually but there is not interface for this
  * Akhil will communicate with Qian to request list of patches

* KNI IOVA patch by Marvel waiting for review


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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-07-04 10:11 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-04 10:11 [dpdk-dev] DPDK Release Status Meeting 4/7/2019 Ferruh Yigit

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).