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 11/02/2021
Date: Thu, 11 Feb 2021 11:36:49 +0000 [thread overview]
Message-ID: <832e29dd-1589-d5ed-9e2f-8d2a1941ec32@intel.com> (raw)
Meeting minutes of 11 February 2021
-----------------------------------
Agenda:
* Release Dates
* -rc3 status
* Subtrees
* LTS
* Opens
Participants:
* Canonical
* Debian/Microsoft
* Intel
* NXP
* Nvidia
Release Dates
-------------
* v21.02 dates
* -rc3 is released on Friday, 5 February 2021
* http://inbox.dpdk.org/dev/5305610.D7H1GXTtC2@thomas/
* Release pushed to *Sunday, 14 February 2021*
* v21.05 draft dates, please comment:
* Proposal/V1: Thursday, 18 March
* -rc1: Thursday, 15 April
* Release: Friday, 14 May
* Reminder of roadmaps for 21.05.
-rc3 status
-----------
* Intel sent test results, validation almost completed, all looks good:
* http://inbox.dpdk.org/dev/8a317b8958854b6fbdf1af323345cf12@intel.com/
* IBM and Red Hat sent test results for -rc2, both looks good:
*
http://inbox.dpdk.org/dev/2c8bd0f0-8dec-4d84-e7b2-e73cddfd975f@linux.vnet.ibm.com/
*
http://inbox.dpdk.org/dev/519040848.11732713.1612702771429.JavaMail.zimbra@redhat.com/
Subtrees
--------
* main
* Not much patches in the backlog
* Waiting tested platform patches from all vendors
* Marvell not sent yet
* Does it make sense NXP to send one?
* John will help on the release notes
* next-net
* No update after -rc3, patches are going in directly to the main repo
* next-crypto
* No update, no patch in backlog for release
* next-eventdev
* No update
* next-virtio
* No update
* next-net-mlx
* There was a patch, pulled directly to main repo
* next-net-brcm
* No update
* next-net-intel
* Two patches pulled directly to main repo
* next-net-mrvl
* No update, there are Marvell patches but they might be for next release
LTS
---
* v19.11.7
* Christian Ehrhardt started working on it.
* v20.11.x
* Luca will work on it.
* There are some patches waiting response from authors to backport to LTS.
LTS maintainers are contacted for the backport, some of the components waiting
for response is as following, please check:
* hns3, mlx4/5, ice, bnxt
Opens
-----
* Coverity issue solved, can assign issues now
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:[~2021-02-11 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 11:36 Ferruh Yigit [this message]
2021-02-11 12:47 ` Dumitrescu, Cristian
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=832e29dd-1589-d5ed-9e2f-8d2a1941ec32@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).