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 20/02/2020
Date: Thu, 20 Feb 2020 11:25:21 +0000 [thread overview]
Message-ID: <846c664e-eacc-140b-27c4-e19f908568c5@intel.com> (raw)
Minutes 20 February 2020
------------------------
Agenda:
* Release Dates
* -rc3 status
* Subtrees
* OvS
* Opens
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v20.02 dates:
* -rc3 is released on 16 February
* https://mails.dpdk.org/archives/dev/2020-February/157922.html
* -rc4 Friday 21 February 2020
* Release pushed to *Friday 25 February 2020*
* Release date may postponed if any critical issue found in -rc4 testing
* v20.05 *updated* proposal, please comment:
* Proposal/V1: Wednesday 18 March 2020
* Integration/Merge/RC1: Friday 17 April 2020
* Release: Wednesday 20 May 2020
* The update request is based on delays in 20.02
* Release date postponed more taking into PRC holiday on 1-5 May into account
-rc3 Status
-----------
* Intel and Red Hat sent test results, thank you.
* https://mails.dpdk.org/archives/dev/2020-February/158184.html
* https://mails.dpdk.org/archives/dev/2020-February/158285.html
Subtrees
--------
* main
* For pure experimental libraries, there is an library versioning problem
This is critical to be solved for the -rc4, Intel will try to find resource
to work on it.
* https://mails.dpdk.org/archives/dev/2020-February/158012.html
* Devtools will be merged
* Doc/deprecation notices are in the queue
* Requested an early merge from next-net, since some fixes accumulated
* John will start on working release notes review
* next-net
* Bug fixes merged for -rc4, pulled sub-trees
* next-net-crypto
* There are some fixes, Akhil will merge in next a few hours
* examples/fips_validation patch will be merged to main repo by David
* next-net-eventdev
* No update
* next-net-virtio
* Bug fixes merged for -rc4
* next-net-intel
* Bug fixes merged for -rc4
* LTS
* 17.11.10-rc1 released, please test and report results
* https://mails.dpdk.org/archives/dev/2020-January/154915.html
* Waiting for QAT issue
* Release will be postponed one more week
OvS
---
* 2.13 is ready, waiting for announcement
Opens
-----
* Lots of coverity issues fixed, thanks.
* There is a coverity sticker in patchwork now
* https://patches.dpdk.org/project/dpdk/list/
Which reports 14 new defects as of now
* Plan is to trigger coverity scan from the travis
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-02-20 11:25 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=846c664e-eacc-140b-27c4-e19f908568c5@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.