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 23/04/2020
Date: Thu, 23 Apr 2020 14:08:23 +0100 [thread overview]
Message-ID: <a9936ff3-fefb-529c-528f-3c90a54b6e59@intel.com> (raw)
Minutes 23 April 2020
---------------------
Agenda:
* Release Dates
* Subtrees
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v20.05 dates:
* Integration/Merge/RC1 pushed to *Friday 24 April 2020*
* Release: Wednesday 20 May 2020
* PRC holiday on 1-5 May, need to take into account for validation effort
Subtrees
--------
* main
* crypto tree pulled, in progress of pulling next-net
* Not able to review rte_graph, planning to merge it in -rc2
* Merged ring patches from Konstantin and RCU patches from Honnappa
* Looking trace series, planning to have them in -rc1
* Some fixes for eal and vfio merged
* Checking fixes and changes related to ABI, from Ray and Neil
* gcc10 support
* Some fixes are missing
* Fixes can go after -rc1
* Need a long term plan for the new compiler support
* CI checks exists for new compilers
* Hash library not reviewed
* Some patches related atomic discussed in techboard,
not much to do for the release
* Windows, some patches was not ready postponed to 20.08
* Telemetry may go in -rc2
* There will be a new version, possibly today, to make it more generic
* Call to review for Windows patches
* next-net
* closed the tree yesterday, ready for -rc1
* next-crypto
* pulled for -rc1
* There are two existing issues
* Cryptodev ABI versioning, Fiona working on
* Not sure if it will be ready for -rc1
* rte_security issue, mainline is broken as of now
* Fix is in the mail list, should be merged quickly
* next-eventdev
* No more patches for -rc1, already pulled to main
* next-virtio
* Pulled for -rc1
* Some fixes for next -rc
* Mellanox vdpa queue stats patch postponed to next release
* Mellanox vdpa virtq patch requires rebase, it may wait next -rc
* Packet ring vectorized path patch under review, should be OK for -rc2
* Good to ask vector implementation from all architectures
* next-net-intel
* Most patches merged, only some fixes for -rc2
* fm10k still has build errors, postponed to -rc2
* next-net-mlx
* Some small fixes for -rc2
* next-net-mrvl
* All patches merged for -rc1
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:[~2020-04-23 13:08 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=a9936ff3-fefb-529c-528f-3c90a54b6e59@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).