From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 17/10/2019
Date: Thu, 17 Oct 2019 10:59:04 +0100 [thread overview]
Message-ID: <c32a4732-6d00-0232-045e-e41a43eb7d16@intel.com> (raw)
Minutes 17 October 2019
-----------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Conferences
* Opens
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* NXP
* Red Hat
Release Dates
-------------
* v19.11 dates:
* Integration/Merge/RC1 Wednesday 23 October
* For sub-trees Monday 21 October
* Release Friday 22 November
* Proposed dates for 20.02 release on the mail list, please comment
https://mails.dpdk.org/archives/dev/2019-September/143311.html
These dates may affected from the 19.11 delays, please review again.
Subtrees
--------
* main
* David merged some patches and working on KNI/eal patches
* Planning review ABI process patches for rc1
* next-net
* ~80 patches in backlog, trying to make rc1 dates
* Planning to get ethdev API and rte_flow patches (7-8 patchset) for rc1,
testpmd and driver patches may pushed to rc2
* Two new PMDs already merged
* next-net-crypto
* Planning to get 'octeontx2' PMD
* More review required on three patchset
* ipsec-secgw, add fallback session
https://patches.dpdk.org/project/dpdk/list/?series=6833
* ipsec-secgw, set default to IPsec library mode
https://patches.dpdk.org/patch/60349/, 60350, 60351
* security library, CPU Crypto (asked for tech board review)
https://patches.dpdk.org/project/dpdk/list/?series=6727&state=*
* ipsec, inbound SAD series waiting for an update
https://patches.dpdk.org/project/dpdk/list/?series=6790&state=*
* next-net-eventdev
* Some more patches are in the tree waiting for pull
* l2fwd-event app can be pushed to rc2
(update the existing l3fwd for eventdev pushed to next release)
* next-net-virtio (update from David)
* Reviewing Marvin's vhost packed ring performance optimization patch
* Maxim's (own) Virtio vDPA set is at risk, may pushed to next release
* next-net-intel
* Some patches already in the tree waiting for pull
* ice PMD patches for RSS and FDIR patches under review
* ipn3ke PMD patches has some issues, it has risk for rc1,
can be considered for rc2
* LTS
* v18.11.3-rc2 under test
* More test from more companies is welcome
* Target release date is next week
OvS
---
* For TSO support, DPDK patch has been merged
Conferences
-----------
* DPDK Summit North America, Mountain View CA, November 12-13
* CPF results announced
https://www.dpdk.org/event/dpdk-summit-na-mountain-view/
Opens
-----
* Coverity run last week, there are outstanding issues:
https://scan.coverity.com/projects/dpdk-data-plane-development-kit?tab=overview
* Reminder of other static analysis tool for dpdk, lgtm:
https://lgtm.com/projects/g/DPDK/dpdk/?mode=list
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-10-17 9:59 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=c32a4732-6d00-0232-045e-e41a43eb7d16@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).