From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "web@dpdk.org" <web@dpdk.org>,
"bluca@debian.org" <bluca@debian.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] release 18.11.11
Date: Wed, 20 Jan 2021 15:19:03 +0000 [thread overview]
Message-ID: <db1cc3c4-37fe-22ab-071a-50b99f366276@redhat.com> (raw)
In-Reply-To: <2069342.xcBNsM0NAz@thomas>
On 20/01/2021 14:57, Thomas Monjalon wrote:
> 20/01/2021 15:50, Richardson, Bruce:
>> From: Kevin Traynor
>>> -| 18.11.10 | 18.11.11 | December 2020 | December 2020 (LTS) | Kevin
>>> Traynor |
>>> | 19.11.6 | 19.11.7 | March 2021 | November 2021 (LTS) | Luca
>>> Boccassi |
>>> | - | 20.11.1 | March 2021 | November 2022 (LTS) | Kevin
>>> Traynor |
>>> --
>>
>> While I realise this is a roadmap table, I wonder if we should still leave
>> a row entry for 18.11 for a while, to indicate that it is not getting any
>> further updates. Something like:
>>
>> "| 18.11.11 | - | - | December 2020 (Now EOL) | - |"
>
> Yes I agree to keep EOL for at least 6 months.
>
>
Good idea. Previously we had cleaned out the older ones, but keeping it
there for a while is better. If there's no other comments, I will change
on applying. Thanks.
next prev parent reply other threads:[~2021-01-20 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 14:44 Kevin Traynor
2021-01-20 14:50 ` Richardson, Bruce
2021-01-20 14:57 ` Thomas Monjalon
2021-01-20 15:19 ` Kevin Traynor [this message]
2021-01-20 15:01 ` David Marchand
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=db1cc3c4-37fe-22ab-071a-50b99f366276@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--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).