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 28/01/2021
Date: Thu, 28 Jan 2021 11:05:04 +0000 [thread overview]
Message-ID: <382c1781-8752-89ee-7a3f-d8e60b96f18a@intel.com> (raw)
Meeting minutes of 28 January 2021
----------------------------------
Agenda:
* Release Dates
* -rc1 status
* Subtrees
* LTS
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.02 dates
* -rc2 Friday, 29 January 2021
* -rc3 pulled to *Thursday, 4 February 2021*
* Release pulled to *Friday, 12 February 2021*
* Release date adjusted because of the conflict with Chinese New Year, target
is to finalize the release before the Chinese New Year holiday starts.
-rc1 status
-----------
* Intel sent test results, validation completed, no critical issue:
* http://inbox.dpdk.org/dev/ddcde5a760f94e7eb708d508e50e2ac4@intel.com/
Subtrees
--------
* main
* Bruce's 'buildtools/chkincs' series to check includes
* Arm's ring refactoring set
* There are lots of patches related to the build system
* A pmdinfogen error reported
* More detail needed
* Arm build options rework
* Power library changes
* Hoping to get today
* Mingw build error
* There is a new version for the fix
* next-net
* Progressing, sub-trees pulled, some fixes merged
* Target is to close the -rc2 tomorrow but there are still ~90 patches in the
backlog
* Some driver patches may not make the -rc2, first come first served
* There are testpmd fixes, please help on reviewing them
* octeontx_ep waiting for new version
* If main patchset can go in -rc2, adjustments can be done for -rc3, since
it is a new driver it should be OK, this gives an additional week
* intel raw/ifpga driver is in the backlog
* next-crypto
* no update
* next-eventdev
* Sent pull request
* next-virtio
* Patches merged for -rc2
* Recent virtio defect with -rc1 should be fixed now
* Can consider pulling next-net early to main repo to verify the fix
* Alibaba MMIO patch reviewed
* Alibaba is working on the set for some releases now, deferring it won't
be good
* next-net-mlx
* Two more patches for -rc2, will be ready soon
* next-net-brcm
* no update
* next-net-intel
* no update
* next-net-mrvl
* all merged for -rc2
LTS
---
* v19.11.7
* Christian Ehrhardt will take over the 19.11 maintainership
* v20.11.x
* Luca will take over the 20.11 maintainership from Kevin in long term
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:[~2021-01-28 11:05 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=382c1781-8752-89ee-7a3f-d8e60b96f18a@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).