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/01/2020
Date: Thu, 23 Jan 2020 16:13:14 +0000 [thread overview]
Message-ID: <a8fb0bd9-bc38-775e-adab-7471f4af3901@intel.com> (raw)
Minutes 23 January 2020
-----------------------
Agenda:
* Release Dates
* -rc1 status
* Subtrees
* OvS
* Opens
Participants:
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
Release Dates
-------------
* v20.02 dates:
* -rc1 is released on 21 January
* https://mails.dpdk.org/archives/dev/2020-January/155911.html
* -rc2 Monday 3 February 2020
* -rc3 Monday 10 February 2020
* Release: Friday 14 February 2020
* v20.05 dates:
* Proposal/V1: Friday 6 March 2020
* Integration/Merge/RC1: Friday 10 April 2020
* Release: Friday 1 May 2020
-rc1 Status
-----------
* Overall test results seems good, no major issue found
* Intel testing mostly completed, full coverage will be done after PRC holidays
* There is one major PMD defect which a fix already sent,
rest are minor issues
* Marvell and Microsoft testing is good, no critical issue found
* Mellanox testing found some minor issues
Subtrees
--------
* main
* Windows patches will be reviewed and merged for -rc2 if ready
* IBM vfio patch is on the queue for review
* Kernel modules are disabled in this release, patch already in -rc1
* We need to highlight this change more
* next-net
* Nothing interesting, mostly fixes for -rc2
* mlx vdpa patchset is a big one, planned for -rc2
* next-net-crypto
* Testcase refactoring done
* Inline protocol offload patches from Anoob in the queue
* armv8 crypto patch will be merged today
* SAD patch has some performance drop which may not be possible to avoid
* May go to techboard for decision, functionality vs performance
* CPU crypto will be investigated last, will be considered for -rc2 if
remains enough time after ipsec patches
* next-net-eventdev
* l3fwd sample application will be reviewed, if ready can be merged
next week for -rc2
* next-net-virtio
* No update on the tree after -rc1
* next-net-intel
* Some fix patches
* 'fm10k' patches are postponed to next release
* next-net-mlx
* Some fix patches
* LTS
* 17.11.10-rc1 released, please test and report results
* https://mails.dpdk.org/archives/dev/2020-January/154915.html
* Got test results from Intel, Red Hat & Mellanox
* QAT regression reported by Intel testing, need help from developers
* mlx reported regressions, needs more details
* Will wait above issues to fixed/clarified before release
* 18.11.6-rc2 released, please test and report results
* https://mails.dpdk.org/archives/dev/2020-January/155132.html
OvS
---
* 2.13 in code freezed
Opens
-----
* Coverity run last week, there are outstanding issues, please check:
https://scan.coverity.com/projects/dpdk-data-plane-development-kit?tab=overview
* John sent email to individuals whose patch causing a coverity issue
But everyone is welcome to fix the issues listed
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-01-23 16:13 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=a8fb0bd9-bc38-775e-adab-7471f4af3901@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).