From: Luca Boccassi <Luca.Boccassi@microsoft.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
"web@dpdk.org" <web@dpdk.org>
Cc: "ktraynor@redhat.com" <ktraynor@redhat.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-web] [PATCH v2] update stable tree schedules
Date: Tue, 25 Jun 2019 14:00:02 +0000 [thread overview]
Message-ID: <e93041915aae015d3aabf03fc6e827d3cb3a0abb.camel@microsoft.com> (raw)
In-Reply-To: <20190625134123.12758-1-thomas@monjalon.net>
On Tue, 2019-06-25 at 15:41 +0200, Thomas Monjalon wrote:
> From: Ferruh Yigit <
> ferruh.yigit@intel.com
> >
>
> There is a date level detail for the future stable release dates,
> which
> are mostly not correct because they are far away to know this detail.
> Removing the date detail from the stable release dates and keeping
> only
> month of the year as the release target.
>
> By default putting the next month of the actual release as target for
> stable version release.
>
> Unmaintained branches are removed. 19.02.1 will never happen.
>
> Signed-off-by: Ferruh Yigit <
> ferruh.yigit@intel.com
> >
> Signed-off-by: Thomas Monjalon <
> thomas@monjalon.net
> >
> Acked-by: Luca Boccassi <
> luca.boccassi@microsoft.com
> >
> Acked-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
> content/roadmap/_index.md | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index 1cee44d..02e82a0 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -81,13 +81,8 @@ by 1-2 weeks, depending on the test results.
>
> | Current version | Next version | Next version Date | End of life
> | Maintainer |
> |----------|----------|-------------------|---------------------|---
> -----------------|
> -| 16.11.9 | - | - | March 2019 (LTS) |
> Luca Boccassi |
> | 17.11.6 | 17.11.7 | August 12, 2019 | November 2019 (LTS) |
> Yongseok Koh |
> -| 18.02.2 | - | - | June 2018 |
> Luca Boccassi |
> -| 18.05.1 | - | - | August 2018 |
> Christian Ehrhardt |
> -| 18.08.1 | - | - | April 2019 |
> Kevin Traynor |
> | 18.11.2 | 18.11.3 | September 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 |
> ? |
> -| - | 19.11.1 | February 2020 | November 2021 (LTS) |
> Luca Boccassi |
> +| - | 19.05.1 | September 2019 | September 2019 |
> ? |
> +| - | 19.08.1 | December 2019 | December 2019 |
> ? |
> +| - | 19.11.1 | March 2020 | November 2021 (LTS) |
> Luca Boccassi |
Acked-by: Luca Boccassi <luca.boccassi@microsoft.com>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-06-25 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 16:42 [dpdk-web] [PATCH 1/2] update 18.11.2 schedule Ferruh Yigit
2019-05-16 16:42 ` [dpdk-web] [PATCH 2/2] update stable tree schedules Ferruh Yigit
2019-05-16 16:48 ` Luca Boccassi
2019-05-16 17:15 ` Kevin Traynor
2019-06-25 13:41 ` [dpdk-web] [PATCH v2] " Thomas Monjalon
2019-06-25 14:00 ` Luca Boccassi [this message]
2019-06-25 14:05 ` Thomas Monjalon
2019-05-16 17:12 ` [dpdk-web] [PATCH 1/2] update 18.11.2 schedule Kevin Traynor
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=e93041915aae015d3aabf03fc6e827d3cb3a0abb.camel@microsoft.com \
--to=luca.boccassi@microsoft.com \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.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).