Re: [PATCH] release 20.11.4

[Christian Ehrhardt <christian.ehrhardt@canonical.com>]

On Mon, Jan 17, 2022 at 11:44 AM Kevin Traynor <ktraynor@redhat.com> wrote:
>
> 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 can only agree to Kevin on this.

> 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/

This wasn't lost, but the web-page itself couldn't hold that without
making it ugly and breaking format.
Instead it is present in the commit itself.
As you can see [1] states it as "not yet committing or rejecting the
same to happen later for 20.11 or 21.11"

[1]: https://git.dpdk.org/tools/dpdk-web/commit/?id=6e2f76d0274220b75bfdc4d2bb6d6183fb8b659a

> Anyway, I'm not sure asking validation teams to commit their resources
> in 2023 is realistic 1 year in advance.
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd