From: Kevin Traynor <ktraynor@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH 1/2] update 18.11.2 schedule
Date: Thu, 16 May 2019 18:12:59 +0100 [thread overview]
Message-ID: <29714083-6fd4-0a2d-3d17-4f4bfc71d180@redhat.com> (raw)
In-Reply-To: <20190516164229.33132-1-ferruh.yigit@intel.com>
On 16/05/2019 17:42, Ferruh Yigit wrote:
> 18.11.2 schedule defined more accurately now, updating schedule
> accordingly.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Kevin Traynor <ktraynor@redhat.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 f1dddab..fe9efa6 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -92,7 +92,7 @@ by 1-2 weeks, depending on the test results.
> | 18.02.2 | - | - | June 2018 | Luca Boccassi |
> | 18.05.1 | - | - | August 2018 | Christian Ehrhardt |
> | 18.08.1 | - | - | April 2019 | Kevin Traynor |
> -| 18.11.1 | 18.11.2 | May 31, 2019 | November 2020 (LTS) | Kevin Traynor |
> +| 18.11.1 | 18.11.2 | June 11, 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 | ? |
>
Acked-by: Kevin Traynor <ktraynor@redhat.com>
prev parent reply other threads:[~2019-05-16 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 16:42 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
2019-06-25 14:05 ` Thomas Monjalon
2019-05-16 17:12 ` 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=29714083-6fd4-0a2d-3d17-4f4bfc71d180@redhat.com \
--to=ktraynor@redhat.com \
--cc=ferruh.yigit@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).