From: Kevin Traynor <ktraynor@redhat.com>
To: luca.boccassi@gmail.com, web@dpdk.org
Subject: Re: [PATCH] release 20.11.7
Date: Tue, 13 Dec 2022 13:21:45 +0000 [thread overview]
Message-ID: <2b5f3fd8-e58f-be31-4739-42a3fc9d8e92@redhat.com> (raw)
In-Reply-To: <20221213110446.3802211-1-luca.boccassi@gmail.com>
On 13/12/2022 11:04, luca.boccassi@gmail.com wrote:
> From: Luca Boccassi <bluca@debian.org>
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> ---
> Marking as EOL for now, while we wait to hear if validation teams have capacity for another year
>
> content/download/_index.md | 2 +-
> content/roadmap/_index.md | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/content/download/_index.md b/content/download/_index.md
> index d4292a0..b45108e 100644
> --- a/content/download/_index.md
> +++ b/content/download/_index.md
> @@ -32,7 +32,7 @@ weight = "2"
> | [DPDK 21.08.0](//fast.dpdk.org/rel/dpdk-21.08.tar.xz) | [2021 August 8](//doc.dpdk.org/guides-21.08/rel_notes/release_21_08.html) | de33433a1806280996a0ecbe66e3642f |
> | [DPDK 21.05.0](//fast.dpdk.org/rel/dpdk-21.05.tar.xz) | [2021 May 21](//doc.dpdk.org/guides-21.05/rel_notes/release_21_05.html) | a78bba290b11d9717d1272cc6bfaf7c3 |
> | [DPDK 21.02.0](//fast.dpdk.org/rel/dpdk-21.02.tar.xz) | [2021 February 14](//doc.dpdk.org/guides-21.02/rel_notes/release_21_02.html) | 2c3e4800b04495ad7fa8656a7e1a3ec1 |
> -| [DPDK 20.11.6 (LTS)](//fast.dpdk.org/rel/dpdk-20.11.6.tar.xz) | [2022 August 29](//doc.dpdk.org/guides-20.11/rel_notes/release_20_11.html) | d2c6ee9ca3588ff31c110a04ad7205ac |
> +| [DPDK 20.11.7 (LTS)](//fast.dpdk.org/rel/dpdk-20.11.7.tar.xz) | [2022 December 13](//doc.dpdk.org/guides-20.11/rel_notes/release_20_11.html) | 4c21194a0e535ad7ae45aaa33f1821ea |
> | [DPDK 20.08.0](//fast.dpdk.org/rel/dpdk-20.08.tar.xz) | [2020 August 8](//doc.dpdk.org/guides-20.08/rel_notes/release_20_08.html) | 64badd32cd6bc0761befc8f2402c2148 |
> | [DPDK 20.05.0](//fast.dpdk.org/rel/dpdk-20.05.tar.xz) | [2020 May 26](//doc.dpdk.org/guides-20.05/rel_notes/release_20_05.html) | 7c6f3e7f7de2422775c4cba116012c4d |
> | [DPDK 20.02.1](//fast.dpdk.org/rel/dpdk-20.02.1.tar.xz) | [2020 May 18](//doc.dpdk.org/guides-20.02/rel_notes/release_20_02.html) | fd04cb05c728f474b438c6e7aa1eb195 |
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index e3a4d05..7c8434f 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -135,6 +135,6 @@ by 3-6 weeks, depending on the test results.
> |----------|----------|-------------------|---------------------|---------------------------|
> | 18.11.11 | - | - | December 2020 (EOL) | - |
> | 19.11.13 | 19.11.14 | December 2022 | December 2022 (LTS) | Christian Ehrhardt |
> -| 20.11.6 | 20.11.7 | December 2022 | December 2022 (LTS) | Luca Boccassi, Xueming Li |
> +| 20.11.7 | - | - | December 2022 (EOL) | - |
> | 21.11.2 | 21.11.3 | December 2022 | November 2023 (LTS) | Kevin Traynor |
> | 22.11.1 | 22.11.2 | April 2023 | November 2024 (LTS) | |
I think it's worth to check on the possible i40e regression David found
that I sent on IRC
(http://inbox.dpdk.org/dev/20221213091837.87953-1-david.marchand@redhat.com/).
All the patches in the train were backports for 21.11 and I think it's
serious enough that I will revert them all now before 21.11.3 release.
Other than that the web patch itself looks fine. I have asked Red Hat QE
to confirm on testing 20.11 during 2023.
For the web patch assuming no change in tarball,
Acked-by: Kevin Traynor <ktraynor@redhat.com>
prev parent reply other threads:[~2022-12-13 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 11:04 luca.boccassi
2022-12-13 13:21 ` Kevin Traynor [this message]
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=2b5f3fd8-e58f-be31-4739-42a3fc9d8e92@redhat.com \
--to=ktraynor@redhat.com \
--cc=luca.boccassi@gmail.com \
--cc=web@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).