From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>,
Xueming Li <xuemingl@nvidia.com>
Cc: web@dpdk.org, Luca Boccassi <bluca@debian.org>, xuemingl@dpdk.org
Subject: Re: [PATCH] release 20.11.4
Date: Mon, 17 Jan 2022 10:44:16 +0000 [thread overview]
Message-ID: <8130ced2-60ec-51c1-706d-33df97bb5e19@redhat.com> (raw)
In-Reply-To: <CAJFAV8wdmF6Z2T3k7Xkz6hvmEL30Thu_8E5ViOxMX_VdzZ9feA@mail.gmail.com>
On 17/01/2022 10:03, David Marchand wrote:
> On Mon, Jan 17, 2022 at 9:03 AM Xueming Li <xuemingl@nvidia.com> wrote:
>>
>> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
>> ---
>> 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 83a6881..64aada4 100644
>> --- a/content/download/_index.md
>> +++ b/content/download/_index.md
>> @@ -29,7 +29,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.3 (LTS)](//fast.dpdk.org/rel/dpdk-20.11.3.tar.xz) | [2021 September 6](//doc.dpdk.org/guides-20.11/rel_notes/release_20_11.html) | e2f9ac261eb639c92811d205926253d1 |
>> +| [DPDK 20.11.4 (LTS)](//fast.dpdk.org/rel/dpdk-20.11.4.tar.xz) | [2022 January 17](//doc.dpdk.org/guides-20.11/rel_notes/release_20_11.html) | 61a2ae4e6d8e62a428b549a43d965f4e |
>> | [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 9d3f8e6..7714f22 100644
>> --- a/content/roadmap/_index.md
>> +++ b/content/roadmap/_index.md
>> @@ -139,4 +139,4 @@ by 1-2 weeks, depending on the test results.
>> |----------|----------|-------------------|---------------------|---------------------------|
>> | 18.11.11 | - | - | December 2020 (EOL) | - |
>> | 19.11.11 | 19.11.12 | May 2022 | December 2022 (LTS) | Christian Ehrhardt |
>> -| 20.11.3 | 20.11.4 | December 2021 | November 2022 (LTS) | Luca Boccassi, Xueming Li |
>> +| 20.11.4 | 20.11.5 | May 2022 | December 2023 (LTS) | Luca Boccassi, Xueming Li |
>
> I saw this clearly asked for 19.11 but I don't remember a confirmation
> that validation teams were okay for extending 20.11 to 3 years.
> Otherwise patch lgtm.
>
>
It was discussed that 19.11 should be a *trial* for LTS year 3 support.
From 19.11 year 3 we can see if it is useful and a good use of
resources considering the divergence from main branch and difficulty
backporting/validating.
With the learnings from 19.11 year 3 we can make an informed decision
about other LTSs and it's better not to over commit at this point.
I also made the comment on the 19.11 patch that this was not clear, but
it seems to have got lost.
http://inbox.dpdk.org/web/ab289c72-b055-2dce-0e13-d2252298345c@redhat.com/
Anyway, I'm not sure asking validation teams to commit their resources
in 2023 is realistic 1 year in advance.
next prev parent reply other threads:[~2022-01-17 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 8:03 Xueming Li
2022-01-17 10:03 ` David Marchand
2022-01-17 10:44 ` Kevin Traynor [this message]
2022-01-17 11:15 ` Xueming(Steven) Li
2022-01-17 11:27 ` Christian Ehrhardt
2022-01-17 11:35 ` Kevin Traynor
2022-01-17 12:42 ` [PATCH v1] " Xueming Li
2022-01-18 6:39 ` Christian Ehrhardt
2022-01-19 15:02 ` 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=8130ced2-60ec-51c1-706d-33df97bb5e19@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=web@dpdk.org \
--cc=xuemingl@dpdk.org \
--cc=xuemingl@nvidia.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).