Skip to contentSkip to conversation

doc: update LTS section

PATCH Superseded Kevin Traynor 3 participants 5 messages Feb 7, 2019 – Apr 5, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 doc: update LTS section

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

---
 doc/guides/contributing/stable.rst | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)
doc/guides/contributing/stable.rst +7 -2
index 2ac4f0a88..f1743aeb0 100644
@@ -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
Signature · 1 line
2.19.0
Acked-by on v1 1/1
#1 lore raw
Quoted 5 lines · Kevin Traynor

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

---

Looks good. Just noticed that there's some grammar discrepancy (I see mixing 'an LTS' and 'a LTS' - then again, acronyms always read funny with articles).

Just a funny thing.

Quoted 27 lines
 doc/guides/contributing/stable.rst | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)
doc/guides/contributing/stable.rst +7 -2
index 2ac4f0a88..f1743aeb0 100644
@@ -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 lore raw
Quoted 11 lines · Aaron Conole
Quoted 5 lines · Kevin Traynor

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

---

Looks good. Just noticed that there's some grammar discrepancy (I see mixing 'an LTS' and 'a LTS' - then again, acronyms always read funny with articles).

Thanks - I fixed it, as it would bug me every time I read it :-)

Quoted 4 lines

Just a funny thing.

#3 lore raw

PATCH v2 1/1 doc: update LTS section

In reply to Kevin Traynor

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

---
v2: fixed typo

 doc/guides/contributing/stable.rst | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)
doc/guides/contributing/stable.rst +7 -2
index 2ac4f0a88..48f5f37a8 100644
@@ -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, 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
@@ -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
Signature · 1 line
2.19.0
Acked-by on v2 1/1 Applied
#4 lore raw

07/02/2019 16:39, Kevin Traynor:

Quoted 2 lines

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

The current branches were updated in another patch.

Quoted 3 lines

---

[...]

doc/guides/contributing/stable.rst fixes. Releases should be coordinated with the validation engineers to ensure · line 63

Quoted 2 lines
doc/guides/contributing/stable.rst +2 -0
+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.

I think we could think about some extensions of the LTS period, if there are some volunteers.
But for now, it is documenting the reality :)

Applied, thanks