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 4/7/2019
Date: Thu, 4 Jul 2019 11:11:33 +0100 [thread overview]
Message-ID: <fd7650a0-ddbf-13a8-192e-98dbdce3ac8d@intel.com> (raw)
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.
reply other threads:[~2019-07-04 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fd7650a0-ddbf-13a8-192e-98dbdce3ac8d@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).