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 30/5/2019
Date: Thu, 30 May 2019 16:58:05 +0100 [thread overview]
Message-ID: <6eb18916-108e-aba5-7b8b-d8357ff2dee7@intel.com> (raw)
Minutes 30 May 2019
-------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Conferences
* Opens
Participants:
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* Red Hat
Release Dates
-------------
* v19.08 dates:
* Proposal/V1 Monday 03 June 2019
* Integration/Merge/RC1 Monday 01 July 2019
* 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
* 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
Subtrees
--------
* main
* Nothing critical, weekly merge done, pulled from sub-trees
* rte_ prefix patchset in master, may affect existing patches
* KNI ethtool removal merged
* meson fix by Bruce to fix daily Intel builds is waiting
* next-net
* Merging patches, nothing critical
* Two new PMDs submitted for this release, memif & hinic
* next-eventdev
* Nothing merged yet for 19.08
* next-virtio
* next-crypto
* next-pipeline
* next-qos
* no update received
* Stable trees
* v18.11.2-rc1 is waiting for test
* 11 June is the target release day
* Red Hat and OvS (Ian) tested it
* Waiting test from others like Intel & Mellanox etc..
* Next week is only full week before target release date
* Microsoft will test when possible
OvS
---
* 18.11.2-rc1 validation has been completed
* There is an OvS patch available to use af_xdp PMD, via 19.08.0-rc0
Conferences
-----------
* DPDK Userspace summit: DPDK Userspace · Sept. 19-20, 2019
https://www.dpdk.org/event/dpdk-userspace-bordeaux/
* CFP Opens: Monday, April 29
* CFP Closes: Friday, May 31
* Reminder that CFP closes tomorrow
* US summit dates are not fixed yet
Opens
-----
* There is a potential that 19.11 will be big, need to think about ways to
reduce the risk of delay for the release
* New tool, public-inbox mail archive is enabled:
*
http://inbox.dpdk.org/announce/DB6PR0501MB2167B67F9F92F45A8823C1A5D7180@DB6PR0501MB2167.eurprd05.prod.outlook.com/
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-05-30 15:58 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=6eb18916-108e-aba5-7b8b-d8357ff2dee7@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).