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 18/02/2021
Date: Thu, 18 Feb 2021 13:22:25 +0000 [thread overview]
Message-ID: <d5d1aa89-9cab-7fb7-767e-2f36c6ede39d@intel.com> (raw)
Meeting minutes of 18 February 2021
-----------------------------------
Agenda:
* Release Dates
* 21.02 retrospective
* LTS
Participants:
* Arm
* Canonical
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.02 is released on Sunday, 14 February 2021
* https://mails.dpdk.org/archives/dev/2021-February/199730.html
* https://core.dpdk.org/download/
* https://doc.dpdk.org/guides/rel_notes/release_21_02.html
* v21.05 dates
* Proposal/V1: Thursday, 18 March
* -rc1: Thursday, 15 April
* Release: Friday, 14 May
* Please send roadmaps, preferably before beginning of the release
21.02 retrospective
-------------------
* It was a small release
* For last two years LTS get improved
* It was smoother switch from 19.11 to 20.11
* Bugzilla utilized better, more bugs are closed
* Still there are some long open ones
* Coverity runs automated
* Better coverage on CI with help of meson
* There are not concluded patches long standing in backlog
* Need better support from community to close them
* May consider a meeting to go through them
* No major disruption from new gcc1 compiler
* Release dates mostly predictable, there are small slips but not major ones
* CI can be improved more, we have new CI lead (Aaron)
* Removing dependency to hugepages, devices and root access makes unit tests
easier to be used
* This way it can be run in more platforms and at build time
* Unit tests can be run in the CI with coverage calculation
* The unit test frameworks around: unity, cunity
LTS
---
* v19.11 (next version v19.11.7)
* Received more backports/feedback
* Still waiting response for a few backport
* Will sync with Luca for -rc date
* v20.11 (next version v20.11.1)
* A few more patches waiting for response
* If there is no response, will have the -rc tomorrow
* Can wait next week if there will be backporting
* 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
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-02-18 13:22 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=d5d1aa89-9cab-7fb7-767e-2f36c6ede39d@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).