[dpdk-web] [PATCH v2] add stable and LTS release plan

[Yuanhan Liu <yuanhan.liu@linux.intel.com>]

Cc: John McNamara <john.mcnamara@intel.com>
Cc: Yu Liu <yu.y.liu@intel.com>
Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
---

v2: - some great rewords from John
    - link to the stable contribute guide

    Note that I am not quite sure how the specific release date to be
    added in the Scheduling section. Something like following?

        <p>17.05
        <ul>
                <li>Proposal deadline: February 26
                <li>Integration deadline: March 30
                <li>Release: May 2

                <li>v17.02.1 Release: May 17
                <li>v16.11.2 Release: May 17
        </ul>

---
 dev/roadmap.html | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index dfd5e41..b0fca0f 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -91,6 +91,14 @@
 	integration deadline. Otherwise, they will be postponed to the next releases.
 	<p>At the end of the merge window, the first release candidate is out.
 	<p>The last period is 1 month long and is dedicated to bug fixing.
+	<h3 id="stable">Stable and LTS release</h3>
+	<p>A new release will be made about every 3 months, shortly (around 3
+	weeks) after an upstream release has been made. For example, v16.11.1 was
+	released shortly after v17.02.
+	<p>In general, there will be only one such release for a stable release.
+	For an LTS release, which has a longer maintenance period (2 years),
+	there will be several releases (.2, .3, etc).
+	<p>For more information, please check this <a href="/doc/guides/contributing/stable.html">guidance</a>.
 	<h3 id="dates">Scheduling</h3>
 	<p>16.11
 	<ul>
-- 
1.9.0