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 19/11/2020
Date: Thu, 19 Nov 2020 14:29:53 +0000 [thread overview]
Message-ID: <396d6198-9320-cdc6-a242-cf30aa659681@intel.com> (raw)
Meeting minutes of 19 November 2020
-----------------------------------
Agenda:
* Release Dates
* -rc4 status
* Subtrees
* LTS
* OvS
* Opens
Participants:
* Arm
* Broadcom
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* NXP
* Red Hat
Release Dates
-------------
* v20.11 dates
* -rc4 is released on Friday, 13 November 2020
* http://inbox.dpdk.org/dev/4017285.oMJDOflQix@thomas/
* -rc5: Friday, 20 November 2020
* Release: Wednesday, 25 November 2020
* v21.02 proposal dates, please comment before next meeting:
* Proposal/V1: Sunday, 20 December 2020
* -rc1: Friday, 15 January 2021
* Release: Friday, 5 February 2021
* Please send roadmaps, preferably before beginning of the release
-rc4 status
-----------
* Ping (form Intel) sent the test repot
* https://mails.dpdk.org/archives/dev/2020-November/193037.html
* No new issue except testpmd failed with max-pkt-len param
* Fix patch: https://patches.dpdk.org/patch/84248/
* Please review/test
* Microsoft found some issues and possible performance degradation
* Will create Bugzilla issues for them soon
Subtrees
--------
* main
* Some small fixes for blacklist/whitelist set
* doc and example changes in the queue
* cppchecks fixes
* trivial fixes, can be postponed
* Not much deprecation notice in the backlog
* Can have -r5 tomorrow
* SPSK build issue fixed
* Arm compilation support from Juraj postponed to next release
* next-net
* Pulled from sub-trees, some fixes merged
* A few more fixes and deprecation notices in the queue
* next-crypto
* One patch left, waiting for review
* https://patches.dpdk.org/patch/83391/
* next-eventdev
* There are a few patches in the backlog
* Will send a pull request tomorrow
* next-virtio
* A single fix in the queue, requires a new version
* next-net-intel
* There are still some fixes in the backlog, under review
* next-net-mlx
* Planning the finalize all fixes today/tomorrow
* next-net-mrvl
* No more patch expected for the -rc
* next-net-brcm
* no update
LTS
---
* Next 18.11 release will be 18.11.11
* Going fine, almost finished all patches
* At this stage lots of patches does not apply
* Next 19.11 release will be 19.11.6
* Most of the patches merged
* Some patches are waiting authors to backport
* There is a request for feature backport for PMD
* There are concerns on backporting features
OvS
---
* Validating with DPDK v20.11-rc4, so far no issues
* A patch is under development for meson build
Opens
-----
* No update on the CVE 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 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-11-19 14:30 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=396d6198-9320-cdc6-a242-cf30aa659681@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).