DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: john.mcnamara@intel.com, dev@dpdk.org, bluca@debian.org,
	yskoh@mellanox.com
Cc: aconole@redhat.com, Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-dev] [PATCH] doc: update LTS section
Date: Thu,  7 Feb 2019 15:06:38 +0000	[thread overview]
Message-ID: <20190207150638.11751-1-ktraynor@redhat.com> (raw)

Update the LTS section to mention the branch, how LTS support ends
and update the currently maintained LTS branches.

Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
 doc/guides/contributing/stable.rst | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst
index 2ac4f0a88..f1743aeb0 100644
--- a/doc/guides/contributing/stable.rst
+++ b/doc/guides/contributing/stable.rst
@@ -47,7 +47,8 @@ LTS Release
 A stable release can be designated as an LTS release based on community
 agreement and a commitment from a maintainer. The current policy is that each
-year's November release will be maintained as an LTS for 2 years.
+year's November (X.11) release will be maintained as an LTS for 2 years.
 
-The current DPDK LTS releases are 16.11 and 17.11.
+After the X.11 release, a LTS branch will be created for it at
+http://git.dpdk.org/dpdk-stable where bugfixes will be backported to.
 
 It is anticipated that there will be at least 4 releases per year of the LTS
@@ -57,4 +58,8 @@ fixes. Releases should be coordinated with the validation engineers to ensure
 that a tagged release has been tested.
 
+The current maintained LTS branches are 17.11 and 18.11.
+
+At the end of the 2 years, a final X.11.N release will be made and at that
+point the LTS branch will no longer be maintained with no further releases.
 
 What changes should be backported
-- 
2.19.0

             reply	other threads:[~2019-02-07 15:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 15:06 Kevin Traynor [this message]
2019-02-07 15:22 ` Aaron Conole
2019-02-07 15:42   ` Kevin Traynor
2019-02-07 15:39 ` [dpdk-dev] [PATCH v2] " Kevin Traynor
2019-04-05 13:44   ` Thomas Monjalon
2019-04-05 13:44     ` 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=20190207150638.11751-1-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=aconole@redhat.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --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).