[v2] doc: update LTS section
Checks
Commit Message
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>
Acked-by: Aaron Conole <aconole@redhat.com>
---
v2: fixed typo
doc/guides/contributing/stable.rst | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
Comments
07/02/2019 16:39, Kevin Traynor:
> 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.
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> Acked-by: Aaron Conole <aconole@redhat.com>
> ---
[...]
> +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 :)
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied, thanks
@@ -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