DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>,
	"Stokes, Ian" <ian.stokes@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	"Akhil, Goyal" <akhil.goyal@nxp.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Qian Xu <qian.q.xu@intel.com>, Yongseok Koh <yskoh@mellanox.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 11/4/2019
Date: Thu, 11 Apr 2019 16:43:25 +0100	[thread overview]
Message-ID: <16b375ee-bc7a-1d2e-1815-e2ae12f5f21a@intel.com> (raw)
Message-ID: <20190411154325.kYNtmvtyVxfwLC0yfVt1KR_vUM32oUIYlvXdl4kJ23c@z> (raw)

Minutes 11 April 2019
---------------------

Agenda:
* Release Dates
* Subtrees
* OvS
* Opens


Participants:
* Debian
* Intel
* Mellanox
* RedHat


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

* v19.05 dates:
  * RC1 is released on Friday, 5 April.
    * http://mails.dpdk.org/archives/announce/2019-April/000254.html
  * RC2: Wednesday, 17 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 dates should be discussed soon


Subtrees
--------

* main
  * Thomas will work on rcu and timer library patches for rc2
  * There will be an early merge for rc2 on weekend

* next-net
  * Nothing critical/blocking
  * Will review nbf and ipn3ke PMDs for rc2

* next-virtio
  * No new patches

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

* Stable trees
  * 18.08.1 is released
    * https://mails.dpdk.org/archives/announce/2019-April/000253.html
  * 18.11-1 is released
    * https://mails.dpdk.org/archives/announce/2019-April/000256.html


OvS
---

* OvS master/2.11.x release validated 18.11.1, no issues found
  Will propose to move to that DPDK version


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
  (As of now link is not working for me but hopefully it will come back)


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.

             reply	other threads:[~2019-04-11 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 15:43 Ferruh Yigit [this message]
2019-04-11 15:43 ` Ferruh Yigit
2019-04-12  0:48 ` Rami Rosen
2019-04-12  0:48   ` Rami Rosen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16b375ee-bc7a-1d2e-1815-e2ae12f5f21a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=ian.stokes@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=john.mcnamara@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=yskoh@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).