From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 16/07/2020
Date: Thu, 16 Jul 2020 15:04:42 +0100 [thread overview]
Message-ID: <b7da6c82-5411-5c7d-8f7a-c09c52cd41a0@intel.com> (raw)
Minutes 16 July 2020
--------------------
Agenda:
* Release Dates
* -rc1 status
* Subtrees
* LTS
* OvS
* Opens
Participants:
* Arm
* Debian/Microsoft
* Intel
* Nvidia
* NXP
* Red Hat
Release Dates
-------------
* v20.08 dates:
* -rc1 is released on Sunday, 12 July 2020
* http://inbox.dpdk.org/dev/2553672.smuk0Yhj5f@thomas/
* -rc2 pushed to *Tuesday, 21 July 2020*
* Release: Tuesday, 4 August 2020
* v20.11 proposal dates, please comment:
* Proposal/V1: Wednesday, 2 September 2020
* -rc1: Wednesday, 30 September 2020
* -rc2: Friday, 16 October 2020
* Release: Friday, 6 November 2020
* Please remember to send roadmap for 20.11.
-rc1 status
-----------
* Intel early test result doesn't show any critical issue, tests are going on
* There is a vhost-user performance issue
https://bugs.dpdk.org/show_bug.cgi?id=507
* Reported Red Hat report doesn't show any problem
* https://mails.dpdk.org/archives/dev/2020-July/175029.html
Subtrees
--------
* main
* Some patches are on review for -rc2
* C11 atomic operations
* Waiting for doc update
* Build and tool fixes
* Rest will be deferred to next release
* rte_atomic deprecation, doc part will be reviewed by Stephen
* whitelist/blacklist patchset fails on CI
* To reduce the conflicts it may be merged early 20.11
* next-net
* No ethdev library patch will be accepted after this point
* Pulled from vendor trees but there are more in their backlog
* Expecting more patches will come from vendor trees for -rc2
* intel,mlx,brcm & nxp has waiting patches
* There are driver and testpmd patches in the backlog
* There are multiple bonding patches waiting
* Xavier will support to process them
* Also there is a tap patch not reviewed
* Concern is not many fixes received targeting -rc1, they may not be ready yet
* Target to be ready on Monday, depends to vendor trees too
* next-crypto
* A couple of patches merged rest deferred
* Some patchsets deferred to next release
* Two patchsets from Intel
* multi process crypto application
* add symmetric crypto data-path APIs
* bbdev config application
* It has missing reviews
* next-eventdev
* No update
* next-virtio
* There are some patches ready, Chenbo will list them for merge
* next-net-intel
* Pulled, more patches in the queue
* next-net-mlx
* Two big patches planned for -rc2
* Tx scheduling
* eCPRI support
* Tx scheduling can be ready today, eCPRI on Sunday
LTS
---
* v18.11.9 released
* https://mails.dpdk.org/archives/dev/2020-July/174424.html
OvS
---
* 2.14 feature freeze is close
* It will be using DPDK 19.11.2
* Can OvS use experimental APIs?
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 every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to
"John McNamara <john.mcnamara@intel.com>" for the invite.
reply other threads:[~2020-07-16 14:04 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=b7da6c82-5411-5c7d-8f7a-c09c52cd41a0@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).