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 3/09/2020
Date: Thu, 3 Sep 2020 12:01:34 +0100 [thread overview]
Message-ID: <808e81d6-4181-f686-7561-93d28997b46b@intel.com> (raw)
Meeting minutes of 3 September 2020
-----------------------------------
Agenda:
* Release Dates
* Subtrees
* LTS
* Conferences
* Opens
Participants:
* Arm
* Broadcom
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* NXP
* Red Hat
Release Dates
-------------
* v20.11 dates
* Proposal/V1: Friday, 11 September 2020
* -rc1: Friday, 9 October 2020
* -rc2: Friday, 23 October 2020
* Release: Friday, 13 November 2020
* Nvidia Mellanox, Marvell & Broadcom already sent roadmap, all contributors
please send roadmap for the release.
Subtrees
--------
* main
* There are multiple deprecation notice to close
* Make deprecation is high priority, it may affect many
* There is a CI affect needs to be handled
* python2 deprecation is good to have for release, but not urgent for now
* there are multiple ethdev changes planned, some are still missing
* Some ethdev ABI break in the mail list without deprecation notice
* removing enum MAX values, still not sent a patch
* moving kernel modules to new repo is waiting
* it can be good to move the git history too, if it is easy to do
* We may need to prioritize the features for the release
* To be sure some high priority features addressed for the release
* next-net
* ~200 patches
* Some merged and has pulled from some subtrees
* Ethdev from previous releases are still open
* One new PMD: txgbe
* next-crypto
* Will start working next week
* There is no backup maintainer for crypto tree, good to have one
* Requesting from community to review the patches and support
* There are multiple new PMDs
* next-eventdev
* DLB driver is waiting for v2, which will come soon
* next-virtio
* There are three major patchset
* vhost add vectorized data path
* Virtio vDPA driver
* vhost new featres
* Rest are fixes or small improvements
* next-net-mlx, next-net-intel, next-net-brcm
* Some patches merged and pulled by next-net
* next-net-mrvl
* There are some patches, planning to merge next week
LTS
---
* 18.11.10
* Backporting going on
* -rc1 planned for Monday
* v19.11.4-rc1 is out, please test
* http://inbox.dpdk.org/dev/20200818181222.8462-1-bluca@debian.org/T/#u
* Canonical, Red Hat, Intel, OvS, Nvidia & Microsoft sent test reports.
* Release postponed based on some issues reported by validation
Conferences
-----------
* DPDK Userspace summit 2020 is on September 22 & 23, schedule is online:
https://events.linuxfoundation.org/dpdk-userspace-summit/program/schedule/
* Two days, overall 6 hours (2x3) of talks
* No break between talks
Opens
-----
* Ajit shared the defect backlog in the Bugzilla
* There are some unassigned defects, because of maintainer is not registered
to Bugzilla, not possible to assign them.
* Please all maintainers of the project register to Bugzilla
https://bugs.dpdk.org/
* Copy/Paste from Ajit's notes:
* We have 147 open bugs in UNCONFIRMED/CONFIRMED/IN_PROCRESS state.
* 45 of them are unassigned (assigned to 'dev@dpdk.org' by default)
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-09-03 11:01 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=808e81d6-4181-f686-7561-93d28997b46b@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).