From: Ferruh Yigit <ferruh.yigit@intel.com>
To: web@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-web] [PATCH v2 2/2] update 20.08.0 schedule
Date: Mon, 25 May 2020 14:49:19 +0100 [thread overview]
Message-ID: <20200525134919.3085793-2-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20200525134919.3085793-1-ferruh.yigit@intel.com>
As discussed in
https://mails.dpdk.org/archives/dev/2020-May/168415.html
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
v2:
* Change naming
* "Proposal deadline" -> "Proposal deadline (patch version v1)"
* "Integration deadline" -> "First release candidate (-rc1)"
* Add "Second release candidate (-rc2)"
---
content/roadmap/_index.md | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index dc301e1..7164ba9 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -86,7 +86,10 @@ The last period is 1 month long and is dedicated to bug fixing.
#### 20.08
-- Release: August 2020
+- Proposal deadline (patch version v1): June 12, 2020
+- First release candidate (-rc1): July 8, 2020
+- Second release candidate (-rc2): July 20, 2020
+- Release: August 4, 2020
#### 20.11
--
2.25.4
next prev parent reply other threads:[~2020-05-25 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 19:53 [dpdk-web] [PATCH 1/2] update 20.05.0 schedule 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 ` [dpdk-web] [PATCH 1/2] update 20.05.0 schedule Ferruh Yigit
2020-05-25 13:49 ` [dpdk-web] [PATCH v2 " Ferruh Yigit
2020-05-25 13:49 ` Ferruh Yigit [this message]
2020-05-26 16:04 ` [dpdk-web] [PATCH v2 2/2] update 20.08.0 schedule 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=20200525134919.3085793-2-ferruh.yigit@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).