From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH] scheduling for 2017
Date: Fri, 20 May 2016 17:23:01 +0200 [thread overview]
Message-ID: <1463757781-28862-1-git-send-email-thomas.monjalon@6wind.com> (raw)
Following this proposal:
http://dpdk.org/ml/archives/dev/2016-May/038899.html
The deadlines for 17.02, 17.05 and 17.08 are now detailed.
Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
dev/roadmap.html | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/dev/roadmap.html b/dev/roadmap.html
index b479967..7230b21 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -91,31 +91,37 @@
<p>The last period is 1 month long and is dedicated to bug fixing.
<h3 id="dates">Scheduling</h3>
<p>The release cycles are progressively shorten during 2016.
- <p>Release 16.07
+ <p>16.07
<ul>
<li>Proposal deadline: May 8
<li>Integration deadline: June 16
<li>Release: July 18
</ul>
- <p>Release 16.11
+ <p>16.11
<ul>
<li>Proposal deadline: August 28
<li>Integration deadline: September 30
<li>Release: November 2
</ul>
- <p>Release 17.02
+ <p>17.02
<ul>
+ <li>Proposal deadline: December 4
+ <li>Integration deadline: January 5
<li>Release: February 1
</ul>
- <p>Release 17.05
+ <p>17.05
<ul>
+ <li>Proposal deadline: February 26
+ <li>Integration deadline: March 30
<li>Release: May 2
</ul>
- <p>Release 17.08
+ <p>17.08
<ul>
+ <li>Proposal deadline: May 28
+ <li>Integration deadline: June 29
<li>Release: August 1
</ul>
- <p>Release 17.11
+ <p>17.11
<ul>
<li>Release: November 2
</ul>
--
2.7.0
next reply other threads:[~2016-05-20 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 15:23 Thomas Monjalon [this message]
2016-05-20 15:36 ` Van Haaren, Harry
2016-05-20 15:48 ` Thomas Monjalon
2016-05-20 15:53 ` Van Haaren, Harry
2016-05-24 15:51 ` 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=1463757781-28862-1-git-send-email-thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--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).