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 30/04/2020
Date: Thu, 30 Apr 2020 14:55:47 +0100 [thread overview]
Message-ID: <2ae9cab8-2445-e172-c9b5-046740b138c6@intel.com> (raw)
Minutes 30 April 2020
---------------------
Agenda:
* Release Dates
* -rc1 status
* Subtrees
* OvS
* Opens
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* Red Hat
Release Dates
-------------
* v20.05 dates:
* -rc1 is released on Monday, 27 April
* http://inbox.dpdk.org/dev/2138318.D4D8VRik6i@thomas/
* -rc2 Friday 8 May 2020
* Release: Wednesday 20 May 2020
* v20.08 proposal dates, please comment:
* Proposal/V1: Tuesday, 16 June 2020
* Integration/Merge/RC1: Tuesday, 14 July 2020
* Release: Friday, 7 August 2020
* Please send roadmap for the release
-rc1 status
-----------
* Intel completed majority of tests, no major issue found so far
* Test report will be sent when ready
* Marvel test report also doesn't show any major issue
Subtrees
--------
* main
* Mainly fixes at this moment
* gcc10 fixes
* still not all fixed, should be fixed for -rc2
* eal and ABI patches
* __rte_internal
* working on merging rte_graph and rte_telemetry for -rc2
* bitops is cleanup patch, would be good to have it in -rc1
at this stage it may not make this release
* meson patches from Bruce to fix static linking
May be postponed to next release
* Rawdev for compress+crc multi function, short-term
solution needs to be decided in mail list
* next-net
* Started to merge patches, no big patchset for -rc2
* ethdev patch not accepted because of ABI break, it will need to wait 20.11
* http://inbox.dpdk.org/dev/1923738.gORTcIGjah@thomas/
* ~60 patches in backlog for -rc2
* next-crypto
* no update
* next-eventdev
* Only a few patches for -rc2 to be reviewed
* next-virtio
* Good progress this week, some patches already merged for -rc2
* mlx5 vdpa, packet ring vector path, zero copy optimizations, etc...
* Only a few remaining, PR almost ready
* next-net-intel
* Some fixes for -rc2 has been merged and pulled to next-net
* next-net-mrvl
* ~10 patches to be reviewed for -rc2
OvS
---
* Finished validating stable trees
* OvS 2.11 & 2.12 validated with DPDK 18.11.7
* OvS 2.13 & master branch validated with DPDK 19.11.1
Opens
-----
* Latest coverity scan showed 120 new defects, some of them from old code base,
this may be related to the coverity backend changes
* Need more support to resolve all new issues
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-30 13:55 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=2ae9cab8-2445-e172-c9b5-046740b138c6@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).