From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, John McNamara <john.mcnamara@intel.com>
Subject: Re: [dpdk-web] [PATCH 1/2] remove future short term stable releases
Date: Thu, 28 Mar 2019 17:18:09 +0000 [thread overview]
Message-ID: <91852731-0163-3a81-c4d3-636ef7ab1013@intel.com> (raw)
In-Reply-To: <6673456.Moj3GjLm7S@xps>
On 3/28/2019 5:11 PM, Thomas Monjalon wrote:
> 28/03/2019 18:07, Ferruh Yigit:
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> I think it deserves some explanation.
> Do we really want to remove 19.05.1 and 19.08.1 ?
> Shouldn't we keep a question mark here?
To prevent the impression that they will happen but only not selected the
maintainer yet.
Also our only restriction is not maintainer anymore, it is maintainer + test
resource.
But it can be an option to put more detail in maintainer column instead of "?",
like: "Only if a maintainer and test resource volunteered"
>
>> --- a/content/roadmap/_index.md
>> +++ b/content/roadmap/_index.md
>> @@ -117,6 +117,3 @@ by 1-2 weeks, depending on the test results.
>> | 18.05.1 | - | - | August 2018 | Christian Ehrhardt |
>> | - | 18.08.1 | November 16, 2018 | November 2018 | Kevin Traynor |
>> | - | 18.11.1 | February 15, 2019 | November 2020 (LTS) | Kevin Traynor |
>> -| - | 19.02.1 | May 31, 2019 | June 2019 | ? |
>> -| - | 19.05.1 | August 16, 2019 | September 2019 | ? |
>> -| - | 19.08.1 | November 29, 2019 | December 2019 | ? |
>>
>
>
>
>
>
prev parent reply other threads:[~2019-03-28 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 17:07 Ferruh Yigit
2019-03-28 17:07 ` [dpdk-web] [PATCH 2/2] update stable tree dates Ferruh Yigit
2019-03-28 17:11 ` [dpdk-web] [PATCH 1/2] remove future short term stable releases Thomas Monjalon
2019-03-28 17:18 ` Ferruh Yigit [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=91852731-0163-3a81-c4d3-636ef7ab1013@intel.com \
--to=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--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).