From 219a6e74cab5c6a8cefc7bd2b0f18275835fef2f Mon Sep 17 00:00:00 2001 From: Kevin Traynor Date: Thu, 7 Feb 2019 15:39:58 +0000 Subject: [PATCH] doc: update LTS section Update the LTS section to mention the branch and how LTS support ends. Signed-off-by: Kevin Traynor Acked-by: Aaron Conole Acked-by: Thomas Monjalon --- doc/guides/contributing/stable.rst | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst index b63cd4228c..6a5eee9bd4 100644 --- a/doc/guides/contributing/stable.rst +++ b/doc/guides/contributing/stable.rst @@ -48,9 +48,10 @@ 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 17.11 and 18.11. +After the X.11 release, an 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 or approximately 1 every 3 months. However, the cadence can be shorter or @@ -58,6 +59,11 @@ longer depending on the number and criticality of the backported 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.20.1