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 27/6/2019
Date: Thu, 27 Jun 2019 11:50:36 +0100 [thread overview]
Message-ID: <0e6f7fb1-042a-e63e-7573-c06a58255223@intel.com> (raw)
Minutes 27 June 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
* Release Thurs 01 August
* Reminder to send roadmaps for the release, it helps planning
* Intel, Arm & Mellanox already shared the roadmap
* Marvell will have new PMDs and will provide a roadmap
* v19.11 dates:
* Proposal/V1 Friday 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
Subtrees
--------
* main
* Lots of patches in the backlog
* Some features can be pushed to RC2, list is not clear yet
* There will be early merge this weekend with whatever ready
* Sub-trees should be ready for RC1 until next Wednesday
* next-net
* Merging patches, more to go, nothing blocker
* Will be ready for early merge for end of week
* Target to get hinic PMD for rc1
* next-virtio
* A few patches remaining
* Some patches sent late, not sure to have them in this release
* next-crypto
* Applying patches, waiting new versions for some of them
* Waiting for reviews from component owners Fiona, Shally etc..
* next-eventdev
* Some patchset remaining
* Pull request for RC1 will be ready next Wednesday
* next-net-mrvl
* There will be a new version for octeontx2
* There is no dependency for net driver, but some features for eventdev PMD
depends to net driver, those dependent parts will be separate patchset and
can target rc2
* Stable trees
* Kevin started backporting patches for 18.11.3, rc will happen after he turn
back from holiday
* v17.11.7 rc in coming weeks
OvS
---
* DPDK 18.11.2 tested on master, OvS 2.12 will be using this version
* David send vhost queue number reset patch, this will require DPDK 18.11.2 as
minimum required version because of know fix in DPDK side
* Rebased 'dpdk-master' to 'master'
Opens
-----
* Patchwork shows build failure for most of the patches, can it be possible to
trigger them manually to try again? Qian will check this option.
* Sub-trees should rebase on master to get the build fixes
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-06-27 10:50 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=0e6f7fb1-042a-e63e-7573-c06a58255223@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).