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 13/6/2019
Date: Thu, 13 Jun 2019 11:33:51 +0100 [thread overview]
Message-ID: <f5aabc7b-ad3d-d874-c5f6-efe25c17d31e@intel.com> (raw)
Minutes 13 June 2019
--------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Opens
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v19.08 dates:
* 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
* Mellanox will send the roadmap soon
* v19.11 proposed 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
* next-net to check final checks to include into merge
* No specific patches highlight, requires attention at this stage
* next-net
* Merging patches, nothing critical
* memif PMD merged
* There are two more new PMDs this release, hinic & oncteontx2
* next-virtio
* Pulled previous week
* More patches to merge next week
* Decided to merge virtio-crypto patches into crypto tree, latest desicion:
* vhost-crypto patches ==> "next-net-virtio" tree
* virtio-crypto pathces ==> "next-crypto" tree
* Maxime and Akhil will synchronize/help each-other on reviewing them
* next-crypto
* Review and applying patches going on
* next-eventdev
* no update received
* next-pipeline
* next-qos
* Will drop these trees from the meeting and minutes, because of low traffic
and missing attendance
* Stable trees
* v18.11.2 is released on 11 June, thanks to Kevin. It is a big release.
https://mails.dpdk.org/archives/announce/2019-June/000267.html
https://fast.dpdk.org/rel/dpdk-18.11.2.tar.xz
http://core.dpdk.org/download/
OvS
---
* Looking to integrate 18.11.2 into OvS 2.12
* Integrated "rte_" prefix patch
* Working in Travis support
* Will rebase 'dpdk-latest' branch on top of master
Opens
-----
* Please fix Coverity issues
* There may be an issue in automated checks, Ferruh will follow up
* Need to send a web page patch for roadmap
* Intel target date to replace legacy filtering with rte_flow is 20.05,
will discuss more
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-13 10:33 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=f5aabc7b-ad3d-d874-c5f6-efe25c17d31e@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).