DPDK website maintenance
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: web@dpdk.org
Cc: thomas@monjalon.net, yliu@fridaylinux.org,
	Luca Boccassi <bluca@debian.org>
Subject: [dpdk-web] [RFC v3] Add LTS section on the roadmap page
Date: Tue,  6 Mar 2018 19:43:54 +0000	[thread overview]
Message-ID: <20180306194354.19891-1-bluca@debian.org> (raw)
In-Reply-To: <20180209130440.20380-1-bluca@debian.org>

Signed-off-by: Luca Boccassi <bluca@debian.org>
---
 dev/roadmap.html | 36 +++++++++++++++++++++++++++++++++++-
 1 file changed, 35 insertions(+), 1 deletion(-)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index 569d8b8..ebb81a9 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -37,7 +37,7 @@
 		</ul>
 	</nav>
 </header>
-<section>
+<section id="rel">
 	<h2>Development roadmap</h2>
 	<p>Major known features and milestones may be noted here.
 	This list is obviously neither complete nor guaranteed.
@@ -96,5 +96,39 @@
 		<li>Integration deadline: October 5, 2018
 		<li>Release: November 2, 2018
 	</ul>
+	<h2 id="stable">Stable releases</h2>
+	<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".
+	<p>Developers can provide stable-specific patches by sending them 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.
+	<hr>
+	<table>
+		<tr>
+			<th>Branch</th>
+			<th>Next version</th>
+			<th>Date</th>
+			<th>End of life</th>
+			<th>Maintainer</th>
+		</tr>
+		<tr>
+			<td>16.11</td>
+			<td>16.11.6</td>
+			<td>May 19, 2018</td>
+			<td>November 2018</td>
+			<td>Luca Boccassi</td>
+		</tr>
+		<tr>
+			<td>17.11</td>
+			<td>17.11.2</td>
+			<td>May 19, 2018</td>
+			<td>November 2019</td>
+			<td>Yuanhan Liu</td>
+		</tr>
+	</table>
 </section>
 <footer></footer>
-- 
2.14.2

  parent reply	other threads:[~2018-03-06 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 18:21 [dpdk-web] [RFC] " Luca Boccassi
2018-02-08 18:24 ` Luca Boccassi
2018-02-08 20:42   ` Thomas Monjalon
2018-02-09 13:05     ` Luca Boccassi
2018-02-09 13:04 ` [dpdk-web] [RFC v2] " Luca Boccassi
2018-03-06 11:25   ` Thomas Monjalon
2018-03-06 19:45     ` Luca Boccassi
2018-03-06 19:43   ` Luca Boccassi [this message]
2018-03-08 22:47     ` [dpdk-web] [RFC v3] " 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=20180306194354.19891-1-bluca@debian.org \
    --to=bluca@debian.org \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    --cc=yliu@fridaylinux.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).