From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, ferruh.yigit@intel.com,
david.marchand@redhat.com,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 22/07/2021
Date: Thu, 22 Jul 2021 22:22:15 +0200 [thread overview]
Message-ID: <2408778.Y4KsVIyxDQ@thomas> (raw)
Release Dates
-------------
* v21.08
- Proposal/V1: Wednesday, 2 June (completed)
- rc1: Saturday, 10 July (completed)
- rc2: Friday, 23 July
- rc3: Thursday, 29 July
- rc4: Wednesday, 4 August
- Release: Friday, 6 August
Subtrees
--------
* next-net
- Bug with libatomic in clang, fixed today.
* next-crypto
- Pulled yesterday.
- Only deprecation notices left for this release.
- ABI check on FreeBSD: fixed today.
* next-eventdev
- Few patches for -rc3.
* next-virtio
- Pulled yesterday.
- One more series to look at (was rejected later).
- Change on async experimental code - candidate for -rc3
* next-net-brcm
- No update.
* next-net-intel
- No update.
* next-net-mlx
- Integration in progress
* next-net-mrvl
- Few patches for -rc3.
LTS
---
DPDK 19.11.9 released on Monday by Christian.
Call for help for 19.11.x to fix issues with new toolchains, kernels, etc.
reply other threads:[~2021-07-22 20: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=2408778.Y4KsVIyxDQ@thomas \
--to=thomas@monjalon.net \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
/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).