From: Luca Boccassi <bluca@debian.org>
To: "dev@dpdk.org" <dev@dpdk.org>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] 20.11.3 patches review and test
Date: Mon, 23 Aug 2021 16:30:10 +0100 [thread overview]
Message-ID: <b45ce9723129aa0e983b8ed4910ffbf3f4f100d5.camel@debian.org> (raw)
In-Reply-To: <SJ0PR11MB51504F4E87D0CE84F3EE8164FEFA9@SJ0PR11MB5150.namprd11.prod.outlook.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of luca.boccassi@gmail.com
> Sent: Monday, August 9, 2021 4:44 PM
> To: stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Akhil Goyal <akhil.goyal@nxp.com>; Ali Alnubani <alialnu@nvidia.com>;
> Walker, Benjamin <benjamin.walker@intel.com>; David Christensen
> <drc@linux.vnet.ibm.com>; Govindharajan, Hariprasad
> <hariprasad.govindharajan@intel.com>; Hemant Agrawal
> <hemant.agrawal@nxp.com>; Stokes, Ian <ian.stokes@intel.com>; Jerin
> Jacob <jerinj@marvell.com>; Mcnamara, John <john.mcnamara@intel.com>;
> Ju-Hyoung Lee <juhlee@microsoft.com>; Kevin Traynor
> <ktraynor@redhat.com>; Luca Boccassi <bluca@debian.org>; Pei Zhang
> <pezhang@redhat.com>; Yu, PingX <pingx.yu@intel.com>; Xu, Qian Q
> <qian.q.xu@intel.com>; Raslan Darawsheh <rasland@nvidia.com>; Thomas
> Monjalon <thomas@monjalon.net>; Peng, Yuan <yuan.peng@intel.com>;
> Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Subject: [dpdk-dev] 20.11.3 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 20.11.3.
>
> The planned date for the final release is August 23rd.
>
> Please help with testing and validation of your use cases and report
any
> issues/results with reply-all to this mail. For the final release the
fixes and
> reported validations will be added to the release notes.
>
> A release candidate tarball can be found at:
>
> https://dpdk.org/browse/dpdk-stable/tag/?id=v20.11.3-rc1
>
> These patches are located at branch 20.11 of dpdk-stable repo:
> https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Luca Boccassi
Hello,
The release of 20.11.3 is postponed to September the 6th to allow more
time for regression tests to complete. Apologies for any issues this
delay will cause.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2021-08-23 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 8:43 luca.boccassi
2021-08-13 11:42 ` Jiang, YuX
2021-08-13 13:31 ` Luca Boccassi
2021-08-13 14:25 ` David Hunt
2021-08-23 15:30 ` Luca Boccassi [this message]
2021-08-26 10:09 ` Christian Ehrhardt
2021-08-26 12:20 ` Luca Boccassi
2021-08-19 12:10 ` Ali Alnubani
2021-08-19 14:31 ` Luca Boccassi
2021-08-23 2:37 ` Pei Zhang
2021-08-23 10:08 ` Luca Boccassi
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=b45ce9723129aa0e983b8ed4910ffbf3f4f100d5.camel@debian.org \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).