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 7/3/2019
Date: Thu, 7 Mar 2019 12:22:01 +0000 [thread overview]
Message-ID: <fbe3e28d-709e-84cd-f6f3-4bb06aa332f1@intel.com> (raw)
Minutes 7 March 2019
--------------------
Agenda:
* Release Dates
* Subtrees
* Opens
Participants:
* Arm
* Debian
* Intel
* Mellanox
* NXP
* RedHat
Release Dates
-------------
* v19.05 dates, no change:
* Proposal Deadline has ended on 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
There is a discussion about deadline, to give more time between rc1 and
the release, please comment, if no objection we can update proposal:
https://mails.dpdk.org/archives/dev/2019-February/125000.html
Subtrees
--------
* main
* More patches planned to be merged today/tomorrow
* Thomas will check eal patches
* Will work on 'experimental' tag to remove, initially on 'eal' and 'ehtdev'
libraries. Volunteers to check other libraries are welcome.
* Planning a merge from sub-trees on the end of the week
* Features of the release to pay attention:
* Arm locking patches
* Need more review
* Windows patches
* May get only preparation patches for this relase
* Team is working on and target initial 'hello world' patchset upstream
* Mellanox is willing to contribute to the work, Thomas will organize
companies next week to work together including Microsoft.
* next-net
* nothing critical/urgent at this point
* Four new PMDs, af_xdp, memif, ifpga ipn3ke, netcope nfb
* Need to start merging them, leaving them to the rc1 deadline will be risky
for the PMDs. Will ping authors in the background if attention required.
* memif has a dependency, need to resolve, needs review:
* http://patchwork.dpdk.org/patch/49009/
* next-virtio
* reviews and new version of patches going on
* not much merge expected this week
* next-crypto
* There will be some merges this week
* _Need support on BBDev and Compressdev work_
* next-eventdev
* next-pipeline
* next-qos
* No update, we need attendance from maintainers
* Stable trees
* 18.11-1-rc1 is out, waiting to be tested
* 16.11.9-rc2 Intel test result found some errors, Qian will sync more with
Luca on details.
* With release 17.11.5 Intel test result found some errors, Qian to send a
public report for the errors.
* 18.08.1-rc3 is waiting for more test
* RedHat validated virtualization part of it, needs more test
* It is not in current plans of Intel to test it
* Mellanox is not interested with 18.08.1
* With the missing interest and testing, should drop the 18.08.1 stable
release? We need comment from community.
* Including missing maintainer for 19.02 stable and lack of interest to
18.08, a wider question, should we drop short term stable releases
altogether? Need to discuss in mail list.
Opens
-----
* Akhil is looking for co-maintainer for crypto sub-tree,
any volunteer please contact to Akhil or Thomas.
* DPDK stinks? Luca tested Sonarcloud static analysis tool, he says '(22000 code
smells flagged)'. More details on his email:
https://mails.dpdk.org/archives/dev/2019-March/125887.html
* Need John McNamara's input to compare Sonarcloud with Coverity
* We need to figure out if Sonarcloud can be static analysis tool solution for
DPDK
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-07 12:22 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=fbe3e28d-709e-84cd-f6f3-4bb06aa332f1@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).