From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] [draft] DPDK Release Status Meeting 11/10/2018
Date: Thu, 11 Oct 2018 12:32:32 +0100 [thread overview]
Message-ID: <1d374c5f-7323-d3f4-a48d-6ef82afebc40@intel.com> (raw)
Minutes 11 October 2018
----------------------
Agenda:
* Dates
* Subtrees
* Bugzilla
* Pcap
* Coverity
Participants:
* Intel
* RedHat
* Mellanox
* NXP
* Broadcom
* Arm
Release Dates
-------------
* RC1 date *pushed half a week*, it is now *Wednesday, 17th October 2018*
* Delay is because of existing patch backlog.
Subtrees
--------
* main
* Not a lot of updates during the week
* Will pull from sub-trees today
* Then will pull Bus and Hot-plug - Try for today/tomorrow
* Telemetry and Power features are waiting to be merged
* next-net
* ~50 patches in the backlog
* New PMD (Atlantic) and some reviews are going on, these may go in on rc2
* For rc1, rte_flow patches, hotplug patches by Thomas and pull form
next-net-mlx are waiting
* Could be ready by Monday
* next-crypto
* Akhil is out today, Shreyansh gave brief update
* Not much backlog left. ~20.
* next-virtio
* 2 main features to get ready
* Can be ready soon and some patches can be merged on rc2
* next-eventdev
* Already pulled
* Build issue solved
* next-pipeline
* next-qos
* Pull request sent, waiting for pull
Bugzilla
--------
* Nothing major
PcapPlusPlus
------------
* A project with DPDK wrapper
* https://mails.dpdk.org/archives/web/2018-October/000897.html
Coverity
--------
* Coverity is broken for DPDK
* John is doing manual Coverity builds and upload, analysis not working
* Ferruh will try next-net Coverity project
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 and email and I will send you the invite.
next reply other threads:[~2018-10-11 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 11:32 Ferruh Yigit [this message]
2018-10-11 12:31 ` Ferruh Yigit
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=1d374c5f-7323-d3f4-a48d-6ef82afebc40@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).