From: Kevin Traynor <ktraynor@redhat.com>
To: web@dpdk.org
Cc: bluca@debian.org, christian.ehrhardt@canonical.com,
xuemingl@nvidia.com, thomas@monjalon.net, ferruh.yigit@intel.com,
david.marchand@redhat.com
Subject: Re: [PATCH v3 2/2] add 21.11 LTS roadmap
Date: Mon, 21 Feb 2022 10:14:27 +0000 [thread overview]
Message-ID: <c9e97f12-12c5-670c-aa08-86246bacc81b@redhat.com> (raw)
In-Reply-To: <20220113101915.190233-2-ktraynor@redhat.com>
On 13/01/2022 10:19, Kevin Traynor wrote:
> Add initial dates and maintainer for 21.11 LTS
> as approved by Techboard in
> http://mails.dpdk.org/archives/dev/2021-December/230920.html
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> content/roadmap/_index.md | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index cf212a4..326173a 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -143,2 +143,3 @@ by 3-6 weeks, depending on the test results.
> | 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 |
> +| 21.11.0 | 21.11.1 | April 2022 | November 2023 (LTS) | Kevin Traynor |
I applied these as there is some incoming questions about LTS versions.
Thanks.
prev parent reply other threads:[~2022-02-21 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 12:19 [PATCH 1/2] add link in stable release section and update typical timeframe Kevin Traynor
2022-01-11 12:19 ` [PATCH 2/2] add 21.11 LTS roadmap Kevin Traynor
2022-01-11 12:39 ` Thomas Monjalon
2022-01-11 12:43 ` [PATCH 1/2] add link in stable release section and update typical timeframe Thomas Monjalon
2022-01-11 13:22 ` Kevin Traynor
2022-01-13 10:19 ` [PATCH v3 " Kevin Traynor
2022-01-13 10:19 ` [PATCH v3 2/2] add 21.11 LTS roadmap Kevin Traynor
2022-02-21 10:14 ` 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=c9e97f12-12c5-670c-aa08-86246bacc81b@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
--cc=web@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).