From: Ferruh Yigit <ferruh.yigit@intel.com>
To: web@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-web] [PATCH 1/2] update 20.05.0 schedule
Date: Fri, 22 May 2020 20:58:02 +0100 [thread overview]
Message-ID: <661c4a65-9204-52d9-0122-1c1cf06ee1ea@intel.com> (raw)
In-Reply-To: <20200522195338.1012290-1-ferruh.yigit@intel.com>
On 5/22/2020 8:53 PM, Ferruh Yigit wrote:
> -rc1 updated to 24 April as discussed in
> https://mails.dpdk.org/archives/dev/2020-April/165097.html
> (-rc1 already released on 27 April, updating it to be accurate)
>
> release date updated to 26 May as discussed in
> https://mails.dpdk.org/archives/dev/2020-May/168415.html
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> content/roadmap/_index.md | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index 114f439..dc301e1 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -81,8 +81,8 @@ The last period is 1 month long and is dedicated to bug fixing.
> #### 20.05
>
> - Proposal deadline: March 18, 2020
> -- Integration deadline: April 17, 2020
> -- Release: May 20, 2020
> +- Integration deadline: April 24, 2020
> +- Release: May 26, 2020
>
> #### 20.08
>
>
It may be good idea to update the roadmap web page when a schedule update has
been decided in the release status meeting. To more clearly communicate the
decided new dates.
I will try to follow it as much as I can, feel free to remind when forgotten :)
next prev parent reply other threads:[~2020-05-22 19:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 19:53 Ferruh Yigit
2020-05-22 19:53 ` [dpdk-web] [PATCH 2/2] update 20.08.0 schedule Ferruh Yigit
2020-05-23 20:15 ` Thomas Monjalon
2020-05-25 13:38 ` Ferruh Yigit
2020-05-22 19:58 ` Ferruh Yigit [this message]
2020-05-25 13:49 ` [dpdk-web] [PATCH v2 1/2] update 20.05.0 schedule Ferruh Yigit
2020-05-25 13:49 ` [dpdk-web] [PATCH v2 2/2] update 20.08.0 schedule Ferruh Yigit
2020-05-26 16:04 ` Thomas Monjalon
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=661c4a65-9204-52d9-0122-1c1cf06ee1ea@intel.com \
--to=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).