DPDK website maintenance
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: web@dpdk.org
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
	Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Yu Liu <yu.y.liu@intel.com>
Subject: [dpdk-web] [PATCH] add stable and LTS release plan
Date: Mon, 23 Jan 2017 20:10:46 +0800	[thread overview]
Message-ID: <1485173446-30737-1-git-send-email-yuanhan.liu@linux.intel.com> (raw)

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>
---

  I made it in rush, meaning there are huge room for improvements
  about this short update :)

  Another thought from me is to link the detailed stable/LTS doc
  from John, when it's merged.
---
 dev/roadmap.html | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index dfd5e41..3964422 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -91,6 +91,13 @@
 	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 (about 3
+	weeks) after an upstream release is made. For example, v16.11.1 will
+	be released shortly after v17.02 is released.
+	<p>For a stable release, normally, there is only one such release.
+	While for a LTS release, which has longer maintainance (2 years),
+	there are more releases (.2, .3, etc) following.
 	<h3 id="dates">Scheduling</h3>
 	<p>16.11
 	<ul>
-- 
1.9.0

             reply	other threads:[~2017-01-23 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 12:10 Yuanhan Liu [this message]
2017-02-24  9:59 ` Thomas Monjalon
2017-02-24 10:42   ` Mcnamara, John
2017-02-28  7:02     ` Yuanhan Liu
2017-02-28  9:10       ` 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=1485173446-30737-1-git-send-email-yuanhan.liu@linux.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=thomas.monjalon@6wind.com \
    --cc=web@dpdk.org \
    --cc=yu.y.liu@intel.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).