From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH v3] update stable releases roadmap
Date: Thu, 17 May 2018 18:32:01 +0200 [thread overview]
Message-ID: <20180517163201.32713-1-thomas@monjalon.net> (raw)
In-Reply-To: <20180309133612.19927-1-thomas@monjalon.net>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: Luca Boccassi <bluca@debian.org>
Acked-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Acked-by: Kevin Traynor <ktraynor@redhat.com>
---
The proposed change of last versions (about shortening delays)
is dropped in this v3, as agreed during discussions in this list
and in the technical board.
---
dev/roadmap.html | 40 +++++++++++++++++++++++++++++++++-------
1 file changed, 33 insertions(+), 7 deletions(-)
diff --git a/dev/roadmap.html b/dev/roadmap.html
index f66c59a..aabdbf4 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -102,13 +102,15 @@
<li>Integration deadline: June 29, 2018
<li>Release: August 1, 2018
</ul>
- <p>18.11
+ <p>18.11 (LTS)
<ul>
<li>Proposal deadline: September 7, 2018
<li>Integration deadline: October 5, 2018
<li>Release: November 2, 2018
</ul>
<h2 id="stable">Stable releases</h2>
+ <p>There is a documentation page describing the
+ <a href="/doc/guides/contributing/stable.html">guidelines of the stable releases</a>.
<p>Stable point releases follow mainline releases.
<p>After each -rc tag and after the final version, relevant bug fixes get
backported by the stable maintainers into the respective branches in "bursts".
@@ -128,17 +130,41 @@
<th>Maintainer</th>
</tr>
<tr>
- <td>16.11.6</td>
- <td>May 19, 2018</td>
- <td>November 2018</td>
+ <td>16.11.7</td>
+ <td>June 8, 2018</td>
+ <td>November 2018 (LTS)</td>
<td>Luca Boccassi</td>
</tr>
<tr>
- <td>17.11.2</td>
- <td>May 19, 2018</td>
- <td>November 2019</td>
+ <td>17.11.3</td>
+ <td>June 8, 2018</td>
+ <td>November 2019 (LTS)</td>
<td>Yuanhan Liu</td>
</tr>
+ <tr>
+ <td>18.02.2</td>
+ <td>June 8, 2018</td>
+ <td>June 2018</td>
+ <td>Luca Boccassi</td>
+ </tr>
+ <tr>
+ <td>18.05.1</td>
+ <td>August 24, 2018</td>
+ <td>August 2018</td>
+ <td>Christian Ehrhardt</td>
+ </tr>
+ <tr>
+ <td>18.08.1</td>
+ <td>November 16, 2018</td>
+ <td>November 2018</td>
+ <td>looking for volunteer</td>
+ </tr>
+ <tr>
+ <td>18.11.1</td>
+ <td>January 11, 2019</td>
+ <td>November 2020 (LTS)</td>
+ <td>Kevin Traynor</td>
+ </tr>
</table>
</div>
</section>
--
2.16.2
next prev parent reply other threads:[~2018-05-17 16:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 13:36 [dpdk-web] [PATCH] " Thomas Monjalon
2018-03-09 13:44 ` Luca Boccassi
2018-03-09 13:49 ` Thomas Monjalon
2018-03-09 14:03 ` [dpdk-web] [dpdk-techboard] " Ananyev, Konstantin
2018-03-09 14:19 ` Thomas Monjalon
2018-03-09 15:24 ` Ferruh Yigit
2018-03-09 15:45 ` Thomas Monjalon
2018-03-09 17:30 ` Luca Boccassi
2018-03-09 14:30 ` [dpdk-web] " Kevin Traynor
2018-03-09 14:51 ` Thomas Monjalon
2018-03-09 15:43 ` Kevin Traynor
2018-03-22 11:03 ` Luca Boccassi
2018-03-22 11:22 ` Luca Boccassi
2018-03-22 11:25 ` Thomas Monjalon
[not found] ` <1522937784.16877.28.camel@debian.org>
2018-04-05 14:19 ` Christian Ehrhardt
2018-04-05 14:23 ` Thomas Monjalon
2018-04-10 23:28 ` [dpdk-web] [PATCH v2] " Thomas Monjalon
2018-04-11 10:04 ` Luca Boccassi
2018-04-11 10:43 ` Christian Ehrhardt
2018-04-11 15:10 ` Kevin Traynor
2018-04-18 9:05 ` Ferruh Yigit
2018-04-18 9:14 ` Thomas Monjalon
2018-04-18 12:28 ` Ferruh Yigit
2018-04-18 13:28 ` Thomas Monjalon
2018-04-19 9:38 ` Kevin Traynor
2018-04-20 15:52 ` [dpdk-web] [dpdk-dev] " Aaron Conole
2018-04-25 8:33 ` Ferruh Yigit
2018-04-25 10:03 ` Luca Boccassi
2018-04-30 10:47 ` Thomas Monjalon
2018-05-01 14:16 ` Aaron Conole
2018-05-01 15:46 ` Kevin Traynor
2018-05-01 16:02 ` Thomas Monjalon
2018-05-17 16:32 ` Thomas Monjalon [this message]
2018-05-17 16:41 ` [dpdk-web] [PATCH v3] " Ferruh Yigit
2018-05-17 16:59 ` 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=20180517163201.32713-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).