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 20/6/2019
Date: Thu, 20 Jun 2019 12:52:06 +0100 [thread overview]
Message-ID: <b32b202b-ec82-8fb1-6733-6907c5f5cef2@intel.com> (raw)
Minutes 20 June 2019
--------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Opens
Participants:
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v19.08 dates:
* RC1 date pushed to *Monday 08 July*
* Release Thurs 01 August 2019
* Reminder to send roadmaps for the release, it helps planning
* Intel and Arm already shared the roadmap
* Marvell will have new PMDs and will provide a roadmap
* Mellanox will send the roadmap soon
* v19.11 dates:
* Proposal/V1 Friday 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
Subtrees
--------
* main
* Will do a sub-trees merge today/tomorrow
* next-net
* Merging patches, more to go
* Will be ready for pull from main at the end of today
* Marvell proposed to have a net vendor sub-tree, which will be pulled by
next-net. Thanks for it, this will help on next-net work load
* For next-net-intel, Xiaolong will cover Qi during holiday
* next-virtio
* Will send a pull request today
* next-crypto
* Will get ipsec patches
* bbdev patches are in backlog, comments sent
* next-eventdev
* Merging patches
* Waiting for new versions of patches
* Stable trees
* Kevin will be on holiday, Luca will cover him for 18.11.x
* v17.11.7 work will start, target is to have rc in two weeks
OvS
---
* Travis patch to track branches integrated
* OvS 2.9/2.10 validating 17.11.6, will help to know 17.11.7 plans
* OvS 2.12, v1: 1 July, feature freeze mid July, release mid August
Opens
-----
* Please fix Coverity issues
* Ferruh to check build errors in daily build log
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-20 11:52 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=b32b202b-ec82-8fb1-6733-6907c5f5cef2@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 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.