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 10/12/2020
Date: Thu, 10 Dec 2020 10:54:13 +0000 [thread overview]
Message-ID: <fce09eda-54f2-11a5-4a51-eed0ddf8b572@intel.com> (raw)
Meeting minutes of 10 December 2020
-----------------------------------
Agenda:
* Release Dates
* Subtrees
* LTS
* OvS
* Opens
Participants:
* Arm
* Broadcom
* Debian/Microsoft
* Intel
* Nvidia
* Red Hat
Release Dates
-------------
* v21.02 dates
* Proposal/V1: Sunday, 20 December 2020
* -rc1: Friday, 15 January 2021
* Release: Friday, 5 February 2021
* Please send roadmaps, preferably before beginning of the release
* Thanks to NTT for sending roadmap
Subtrees
--------
* main
* Tooling/testing patches in the backlog
* There are patches deferred from previous release
* It is preferred to get risky patches early, to give enough time them to be
tested
* Travis not working is a concern for ABI checks
* David sent patch a patch to enable github actions for checks
* https://patches.dpdk.org/project/dpdk/list/?series=14188
* Please test
* Many people will be taking holidays on last two weeks of the year
* next-net
* A few patches reviewed & merged
* No big backlog as of now, nothing interesting
* next-crypto
* No update
* next-eventdev
* No update
* next-virtio
* There are some patches deferred from previous release
* next-net-mlx, next-net-brcm
* Some patches merged and can be pulled
* next-net-intel, next-net-mrvl
* No update
LTS
---
* v19.11.6-rc1 is out, please test
* http://inbox.dpdk.org/dev/20201203093856.299103-1-luca.boccassi@gmail.com/
* Waiting for test reports
* Target release date is 17 December
* v18.11.10 work is going on
* waiting for backports, request emails sent
* Some backports received, waiting for some others
* target is to close the -rc1 before holidays
OvS
---
* OvS side reported a build error related to the pkgconfig flag
* Bruce is investigating it
Opens
-----
* Asaf shared a draft release process documentation
* After review there were no objection to the document, it will be shared
publicly
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-12-10 10:54 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=fce09eda-54f2-11a5-4a51-eed0ddf8b572@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).