All of lore.kernel.org
 help / color / mirror / Atom feed
* [dpdk-dev] DPDK Release Status Meeting 18/4/2019
@ 2019-04-18 10:58 Ferruh Yigit
  0 siblings, 0 replies; only message in thread
From: Ferruh Yigit @ 2019-04-18 10:58 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 18 April 2019
---------------------

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


Participants:
* Arm
* Debian
* Intel
* Mellanox
* RedHat


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

* v19.05 dates, RC2 date pushed to Friday:
  * RC2: *Friday, 19 April*
  * RC3: Monday , 29 April
  * Release: Friday, 10 May

* v19.08 dates:
  * Proposal/V1               Monday 03 June   2019  
  * Integration/Merge/RC1     Monday 01 July   2019  
  * Release                   Thurs  01 August 2019

  * Schedule updated on roadmap page:
    https://core.dpdk.org/roadmap/

* v19.11 proposed dates, please comment.
  * Proposal/V1               Friday 06 September 2019
  * Integration/Merge/RC1     Friday 11 October   2019
  * Release                   Friday 08 November  2019

  * Constrains:
    * PRC holidays on October 1-7 inclusive, rc1 shouldn't overlap with it
    * US DPDK Summit on mid November, better to have release before summit

  * Some historical .11 release dates data:
	17.08: Tue Aug 8
	17.11-rc1: Sat Oct 14 (9 weeks and 4 days)
	17.11: Wed Nov 15 (4 weeks and 4 days)
	Overall 17.11 release took: 14 weeks and 1 day

	18.08: Thu Aug 9
	18.11-rc1: Mon Oct 29 (11 weeks and 4 days)
	18.11: Mon Nov 26 (4 weeks)
	Overall 18.11 release took: 15 weeks and 4 days


RC1 status
----------

* RC1 Intel test results looks good, no major issue detected


Subtrees
--------

* main
  * Merged timer library
  * For RCU there are questions around API/ABI stability (inline functions)
    Leaning to merge as it is

* next-net
  * Ready for rc2, some waiting fixes can go in after rc2
  * If atlantic macsec patches makes on time, can go in rc2
  * Remaining patches won't be able to make the release

* next-virtio
  * Tree prepared for rc2 and merged into next-net

* next-crypto
  * Akhil get some patches today/tomorrow
  * Will be ready for rc2

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

* Stable trees
  * No update


OvS
---

* OvS master/2.11.x release agreed to move 18.11.1
* For DPDK 17.11, OvS decided to skip 17.11.5 and use 17.11.6 since it
  is close to be released
* OvS testing on DPDK Community Lab is up now,
  The discussion is which version of OvS and DPDK to use, using top of
  development branch for both right now, should stick a fixed version for
  OvS?
* af_xdp support on OvS proposed, there were some patches for it


Opens
-----

* Akhil is looking for co-maintainer for crypto sub-tree

* Coverity is up and there are already some fixes hit the mail list,
  this is good progress, as a reminder, coverity dpdk project link:
  https://scan.coverity.com/projects/dpdk-data-plane-development-kit?tab=overview

* A patch to fix all document spelling errors has been sent by John,
  there will be new version of it


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-04-18 10:59 UTC | newest]

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.