From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 8/11/2018
Date: Thu, 8 Nov 2018 13:27:28 +0000 [thread overview]
Message-ID: <fcf02e25-b244-31a2-edcd-cf31044c2dba@intel.com> (raw)
Minutes 8 November 2018
-----------------------
Agenda:
* Dates
* RC2 status
* RC3
* Subtrees
* Bugzilla
* OvS
* Conferences
* Coverity
* Opens
Participants:
* Broadcom
* Cavium
* Debian
* Intel
* Mellanox
* NXP
* RedHat
Release Dates
-------------
* RC1 was out on Monday, 29 October.
* RC2 was out on Tuesday, 6 November.
* RC3 date is *Monday, 12 November*
* Release date is *Tuesday, 20 November 2018*
* 19.02 dates discussion on mail list:
https://mails.dpdk.org/archives/dev/2018-October/116345.html
Proposed dates copy-paste from above thread:
* Proposal deadline Friday 23 November 2018
* Merge deadline Friday 14 December 2018
* RC1 release Friday 21 December 2018
* RCx + Testing Friday 25 January 2019
* Release Friday 1 February 2019
RC2 status
----------
* Blocking IOVA issues, including 32bit one, are resolved. Thanks to Alejandro.
* A performance drop reported on x86 caused by disabling avx512 for GCC.
* Commit 8d07c82b239f ("mk: disable gcc AVX512F support")
* Intel is working on a fix for RC3.
* Jerin reported l3fwd performance drop on arm caused by hash library updates:
* https://mails.dpdk.org/archives/dev/2018-November/118393.html
* Cavium & ARM are working on a fix.
* Target is to fix on RC3 but won't be a blocker, if the issue is not fixed
on time, responsible commit will be reverted on RC3.
* This affects all architectures, Intel should check too.
* Jerin reported build issue that Thomas will include into RC3.
https://patches.dpdk.org/project/dpdk/list/?series=2306 (?)
* Kevin reported that RedHat validation still observing Bug #76.
* Anatoly is trying to reproduce the issue.
* https://bugs.dpdk.org/show_bug.cgi?id=76
* DPDK Open Lab performance testing did not able to identify these
performance issues, worth thinking what to improve there.
RC3
---
* l2fwd rework won't able to make the RC3 and release.
https://patches.dpdk.org/project/dpdk/list/?series=1752
* procinfo changes will be considered for next release.
https://patches.dpdk.org/project/dpdk/list/?series=2297
* There aren't more deprecation notices yet.
* Thomas highlighted hotplug issues/patches requires attention.
Subtrees
--------
* main
* Possible to have more release candidates in this release.
* next-net
* A few patches merged, no critical issue.
* next-crypto
* Three patches are merged, waiting to be pulled.
* next-virtio
* Preparing a pull request for Friday.
* No critical issue.
* next-eventdev
* No patches for RC3.
* next-pipeline
* next-qos
*
* Stable trees
* Kevin checked backports to 18.08, there are around 230 patches,
he will communicate with authors for some of them.
* Luca queried how to hook up stable branches to the CI/OpenLab,
he will join bi-weekly CI meeting to request/discuss this.
Bugzilla
--------
* 2 new issues this week.
* Number of open defects are increasing, Ajit did one pass on them,
planning to do another one.
OvS
---
* Development branch 'dpdk_latest' switched to 18.08, no blocker issue.
* Kevin worked on changes for detach/attach changes.
* Kevin did simple PVP testing, there is no issue.
Conferences
-----------
* DPDK North America summit acceptances are out,
schedule will be announced in the next few days.
Coverity
--------
* Coverity is back online and John run the latest code on it.
* Some issues are real defects, please pay attention to Coverity issues:
https://scan.coverity.com/projects/dpdk-data-plane-development-kit
Opens
-----
* Akhil to get crypto libraries, he got one but will follow for others.
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 me an email and I will send you the invite.
reply other threads:[~2018-11-08 13:27 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=fcf02e25-b244-31a2-edcd-cf31044c2dba@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.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).