From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH] prepare roadmap for first half of 2019
Date: Thu, 22 Nov 2018 11:20:42 +0100 [thread overview]
Message-ID: <20181122102042.22679-1-thomas@monjalon.net> (raw)
Empty sections can be filled for 19.02/19.05 features.
Dates for 19.02 deadlines were proposed on dev@dpdk.org:
http://mails.dpdk.org/archives/dev/2018-October/116345.html
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/roadmap/_index.md | 26 ++++++++++++++++++++++----
1 file changed, 22 insertions(+), 4 deletions(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 24c4e9e..e5fc506 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -35,6 +35,10 @@ This list is obviously neither complete nor guaranteed.
- noisy VNF forward mode in testpmd
- vDPA sample application
+### Version 19.02 (2019 February) {#1902}
+
+### Version 19.05 (2019 May) {#1905}
+
### Nice to have - Future {#future}
----
- multi-process rework
@@ -65,11 +69,25 @@ The last period is 1 month long and is dedicated to bug fixing.
### Scheduling {#dates}
----
-#### 18.11 (LTS)
+#### 19.02
+
+- Proposal deadline: November 29, 2018
+- Integration deadline: December 14, 2018
+- First release candidate: December 21, 2018
+- Last release candidate: January 25, 2019
+- Release: February 1, 2019
+
+#### 19.05
+
+- Release: May 3, 2019
+
+#### 19.08
+
+- Release: August 2, 2019
+
+#### 19.11
-- Proposal deadline: September 7, 2018
-- Integration deadline: October 5, 2018
-- Release: November 2, 2018
+- Release: November 8, 2019
### Stable Releases {#stable}
----
--
2.19.0
next reply other threads:[~2018-11-22 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 10:20 Thomas Monjalon [this message]
2018-11-22 10:32 ` Mcnamara, John
2018-11-25 11:08 ` 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=20181122102042.22679-1-thomas@monjalon.net \
--to=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).