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 12/11/2020
Date: Thu, 12 Nov 2020 11:39:20 +0000 [thread overview]
Message-ID: <5735a4fd-5b51-dc15-9afc-bd8ab70cacfd@intel.com> (raw)
Meeting minutes of 12 November 2020
-----------------------------------
Agenda:
* Release Dates
* Roadmaps
* -rc3 status
* Subtrees
* LTS
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v20.11 dates
* -rc3 is released on Thursday, 5 November 2020
* http://inbox.dpdk.org/dev/1695484.4DzFrLkl2F@thomas/
* -rc4: Friday, 13 November 2020
* -rc5: Friday, 20 November 2020
* Release: Wednesday, 25 November 2020
* v21.02 proposal dates, please comment:
* Proposal/V1: Sunday, 20 December 2020
* -rc1: Friday, 15 January 2021
* Release: Friday, 5 February 2021
Roadmaps
--------
* Targeting a better project management with roadmaps from all contributors in
advance.
* This enables allocating resources according, manage maintainers' time and set
expectations correct.
* The features announced with a roadmap in advance will get priority on
processing/reviews/commits for that release cycle.
* The roadmap should be sent as early as possible, if possible before start of a
release cycle but not later than two weeks after the previous release.
-rc3 status
-----------
* Ping (form Intel) sent the test repot
* https://mails.dpdk.org/archives/dev/2020-November/192242.html
* Nothing critical, found defects are worked on them
* Marvell found an issue on Rx adapter, working on it
Subtrees
--------
* main
* Example build fix patch is out
* Fix is out, trying to figure out the root cause
* Patch to enable building more examples is in the queue
* Mbuf patches looks ready, planning to merge soon
* Stephen's replace blacklist/whitelist with allow/block patch has a new
version
* Luca did detailed review
* Previous comments are addressed
* Bruce reviewed for build and reported build issues
* pipeline doc updates in the queue
* Juraj's Arm build options rework set
* needs more testing
* In suse build environment, there are some arm and PPC build error
* For arm the RHEL 7 compiler for arm is too old
* Can be possible to disable the failing driver and still test the rest
* next-net
* txgbe second set doesn't look ready, most probably will be
postponed to next release
* fixes after first set has been merged
* There are a few ethdev deprecation notices in the queue
* The RFC to replace the 'rte_eth_mirror_*' APIs postponed to next release
* https://patches.dpdk.org/user/todo/dpdk/?series=13606&delegate=319&state=*
* The existing APIs will be removed 21.11, so we have time for this
* Rest are various fixes
* Regularly pulling from vendor trees
* next-crypto
* No update
* next-eventdev
* Pull request sent for -rc4
* There are some new DLB fixes
* Will check them and send another pull request
* next-virtio
* A series for fixes requires new version
* Patch to enable prefetch is under discussion
* It is causing performance drop
* This is a global problem and can be solved in global level
* Performance drop is seen more in the virtio
* vhost sample, removing ioat dependency is under review
* next-net-intel
* Fixes are coming, there are more fixes in the queue
* next-net-mlx
* Fixes are coming, there are more fixes in the queue
* There was a patch changing rte_flow items sizes,
it may affect some drivers + applications
* Fixes are ready, will hit mail list soon
* next-net-mrvl
* No more patch expected for the -rc
* next-net-brcm
* No new patches in the tree
LTS
---
* Next 18.11 release will be 18.11.11
* Half of the backlog processed
* Next 19.11 release will be 19.11.6
* Worked all patches, no surprise
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.
next reply other threads:[~2020-11-12 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 11:39 Ferruh Yigit [this message]
2020-11-12 11:57 ` David Marchand
2020-11-18 6:24 ` Ruifeng Wang
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=5735a4fd-5b51-dc15-9afc-bd8ab70cacfd@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).