From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: dev@dpdk.org, techboard@dpdk.org, bluca@debian.org,
yliu@fridaylinux.org, ktraynor@redhat.com,
christian.ehrhardt@canonical.com, yskoh@mellanox.com
Subject: [dpdk-dev] [PATCH v2] update stable releases roadmap
Date: Wed, 11 Apr 2018 01:28:13 +0200 [thread overview]
Message-ID: <20180410232813.2534-1-thomas@monjalon.net> (raw)
In-Reply-To: <20180309133612.19927-1-thomas@monjalon.net>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
Patch for the website (to web@dpdk.org) Cc'ed to dev@dpdk.org
v2:
- more volunteers
- propose to do .1 release after -rc1 of next branch.
---
dev/roadmap.html | 37 ++++++++++++++++++++++++++++++++-----
1 file changed, 32 insertions(+), 5 deletions(-)
diff --git a/dev/roadmap.html b/dev/roadmap.html
index e6cf640..c7cd7cb 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -97,13 +97,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".
@@ -111,8 +113,9 @@
to stable@dpdk.org only (avoiding dev@dpdk.org).
<p>After all the relevant bugfixes have been backported,
regression tests are ran, and if clear, the stable release is announced.
- <p>Typically a new stable release version follows a mainline release
- by 1-2 weeks, depending on the test results.
+ <p>The first stable release (.1) of a branch should follow
+ its mainline release (.0) by at least two months,
+ after the first release candidate (-rc1) of the next branch.
<hr>
<div style="overflow-x:auto">
<table>
@@ -125,15 +128,39 @@
<tr>
<td>16.11.6</td>
<td>May 19, 2018</td>
- <td>November 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>November 2019 (LTS)</td>
<td>Yuanhan Liu</td>
</tr>
+ <tr>
+ <td>18.02.1</td>
+ <td>April 6, 2018</td>
+ <td>June 2018</td>
+ <td>Luca Boccassi</td>
+ </tr>
+ <tr>
+ <td>18.05.1</td>
+ <td>June 29, 2018</td>
+ <td>October 2018</td>
+ <td>Christian Ehrhardt</td>
+ </tr>
+ <tr>
+ <td>18.08.1</td>
+ <td>October 5, 2018</td>
+ <td>January 2019</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 parent reply other threads:[~2018-04-10 23:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180309133612.19927-1-thomas@monjalon.net>
2018-04-10 23:28 ` Thomas Monjalon [this message]
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 ` [dpdk-dev] [dpdk-web] " 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 ` 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
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=20180410232813.2534-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=techboard@dpdk.org \
--cc=web@dpdk.org \
--cc=yliu@fridaylinux.org \
--cc=yskoh@mellanox.com \
/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).