doc: update LTS section

Update the LTS section to mention the branch and how LTS support ends.

Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
Acked-by: Aaron Conole <aconole@redhat.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
This commit is contained in:
Kevin Traynor 2019-02-07 15:39:58 +00:00 committed by Thomas Monjalon
parent cf6b07d206
commit 219a6e74ca

View File

@ -48,9 +48,10 @@ LTS Release
A stable release can be designated as an LTS release based on community 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 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 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 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 fixes. Releases should be coordinated with the validation engineers to ensure
that a tagged release has been tested. 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 What changes should be backported
--------------------------------- ---------------------------------