From: "Mcnamara, John" <john.mcnamara@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: "Stokes, Ian" <ian.stokes@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Akhil, Goyal" <akhil.goyal@nxp.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
Yongseok Koh <yskoh@mellanox.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Shahaf Shuler" <shahafs@mellanox.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 28/2/2019
Date: Fri, 1 Mar 2019 16:34:50 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F56A4A2@IRSMSX103.ger.corp.intel.com> (raw)
Minutes 28 February 2019
------------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Opens
Release Dates
-------------
* v19.05 dates, no change:
* Proposal Deadline: Friday, 1 March
* RC1: Friday, 29 March
* Release: Friday, 10 May
* Schedule web page updated accordingly:
http://core.dpdk.org/roadmap/#dates
* v19.08 proposal, please comment:
* Proposal/V1 Friday 07 June 2019
* Integration/Merge/RC1 Friday 05 July 2019
* Release Thurs 01 August 2019
Subtrees
--------
* Next-Net
* No updates
* Next-virtio
* Some patches to review
* Next-Crypto
* Patches scheduled. Merged planned for 1 week
* Need a new sub-tree maintainer
* Next-Eventdev
* No patches
* Next-Ip-pipeline
* Some patches available
* Master
* AF_XDP on target for submission in this release
* Questions about Ipsec and QAT additions. Should also be on track.
* The locking patches from ARM will have a big impact. The community
is asked to review and test them carefully.
LTS and stable
--------------
* Intel has completed testing for 16.11.8 or 17.11.5. Some issues were
found but they are currently investigating if these are genuine issues.
* v18.11.1-rc1 and v18.08.1-rc3 are available for testing
OvS
---
* 2.11.0 was released February 28
Static code analysis tools
--------------------------
* Coverity is back but new analyses aren't running
* Some other suggestions:
* CPPcheck: run periodically by Ferruh
* Sonarcloud: https://sonarcloud.io/
* LGTM: https://lgtm.com/
* Infer: https://fbinfer.com/
* We are looking for volunteers to run some of the other tools on the
DPDK code base to see if they are suitable
Opens
-----
* Akhil is looking for co-maintainer for crypto sub-tree,
any volunteer please contact to Akhil or Thomas.
* Coverity is partially back, but new analyses aren't running
* Looking for suggestions from the community for a better or more stable
solutions
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-03-01 16:34 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=B27915DBBA3421428155699D51E4CFE23F56A4A2@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ian.stokes@intel.com \
--cc=jerin.jacob@caviumnetworks.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).