From: Kevin Traynor <ktraynor@redhat.com>
To: christian.ehrhardt@canonical.com, web@dpdk.org,
Ian Stokes <ian.stokes@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Luca Boccassi <bluca@debian.org>,
Xueming Li <xuemingl@nvidia.com>,
David Marchand <dmarchan@redhat.com>,
Pei Zhang <pezhang@redhat.com>,
Raslan Darawsheh <rasland@nvidia.com>,
qian.q.xu@intel.com, Ju-Hyoung Lee <juhlee@microsoft.com>,
Ali Alnubani <alialnu@nvidia.com>,
David Christensen <drc@linux.vnet.ibm.com>,
benjamin.walker@intel.com,
John McNamara <john.mcnamara@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
yuan.peng@intel.com, pingx.yu@intel.com, zhaoyan.chen@intel.com,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
hariprasad.govindharajan@intel.com
Subject: Re: [PATCH 2/2] Extend 19.11.x support period to 3 years
Date: Fri, 3 Dec 2021 14:17:28 +0000 [thread overview]
Message-ID: <ab289c72-b055-2dce-0e13-d2252298345c@redhat.com> (raw)
In-Reply-To: <20211202101822.3364418-3-christian.ehrhardt@canonical.com>
On 02/12/2021 10:18, christian.ehrhardt@canonical.com wrote:
> From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
> It was discussed in various places by now, along with the switch of the
> main development branch to three per year we also want to extend the
> lifetime of the LTS releases.
>
> 19.11.x is the first to pass the two years and we want to extend it to
> three as it still has active users e.g. via Ubuntu 20.04 LTS but also
> potentially many other appliances and/or vendors.
>
I think it should be clear that 19.11 year 3 is a trial and extending
other LTSs >2 years will be evaluated at the end of this. Just so not to
set expectation that this will automatically apply for other LTS
releases too.
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
> content/roadmap/_index.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index 3c01699..1580a8c 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -102,5 +102,5 @@ by 1-2 weeks, depending on the test results.
> | Current version | Next version | Next version Date | End of life | Maintainers |
> |----------|----------|-------------------|---------------------|---------------------------|
> | 18.11.11 | - | - | December 2020 (EOL) | - |
> -| 19.11.10 | 19.11.11 | January 2022 | December 2021 (LTS) | Christian Ehrhardt |
> +| 19.11.10 | 19.11.11 | January 2022 | December 2022 (LTS) | Christian Ehrhardt |
> | 20.11.3 | 20.11.4 | December 2021 | November 2022 (LTS) | Luca Boccassi, Xueming Li |
>
For the 19.11 trial itself,
Acked-by: Kevin Traynor <ktraynor@redhat.com>
next prev parent reply other threads:[~2021-12-03 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 10:18 [PATCH 0/2] Extend stable coverage on the roadmap christian.ehrhardt
2021-12-02 10:18 ` [PATCH 1/2] Delay release of 19.11.11 christian.ehrhardt
2021-12-03 12:27 ` Luca Boccassi
2021-12-03 14:17 ` Kevin Traynor
2021-12-02 10:18 ` [PATCH 2/2] Extend 19.11.x support period to 3 years christian.ehrhardt
2021-12-03 12:28 ` Luca Boccassi
2021-12-03 14:17 ` Kevin Traynor [this message]
2021-12-08 16:16 ` Mcnamara, John
2021-12-14 7:55 ` Christian Ehrhardt
2021-12-14 8:02 ` Mcnamara, John
2021-12-14 8:38 ` Ali Alnubani
2021-12-16 10:56 ` Pei Zhang
2021-12-16 11:12 ` Christian Ehrhardt
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=ab289c72-b055-2dce-0e13-d2252298345c@redhat.com \
--to=ktraynor@redhat.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dmarchan@redhat.com \
--cc=drc@linux.vnet.ibm.com \
--cc=hariprasad.govindharajan@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=pezhang@redhat.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=xuemingl@nvidia.com \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@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).