Skip to content

Commit

Permalink
doc: update LTS maintenance to 3 years
Browse files Browse the repository at this point in the history
The existing official policy was to maintain LTS releases for 2 years.

19.11 and 20.11 LTS releases were maintained for 3 years and there was
not significant issues caused by code divergence from main etc.

Update the policy to indicate 3 years maintenance for LTS releases, but
note that it depends on community support.

Signed-off-by: Kevin Traynor <[email protected]>
Acked-by: Raslan Darawsheh <[email protected]>
Acked-by: John McNamara <[email protected]>
Acked-by: Morten Brørup <[email protected]>
Acked-by: Luca Boccassi <[email protected]>
Acked-by: Xueming Li <[email protected]>
Acked-by: Thomas Monjalon <[email protected]>
  • Loading branch information
kevintraynor authored and tmonjalo committed Jun 20, 2024
1 parent 61d0965 commit 3c60ea7
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion doc/guides/contributing/stable.rst
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,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 (X.11) release will be maintained as an LTS for 2 years.
year's November (X.11) release will be maintained as an LTS for 3 years,
however that is dependent on continued community support for validation.

After the X.11 release, an LTS branch will be created for it at
https://git.dpdk.org/dpdk-stable where bugfixes will be backported to.
Expand Down

0 comments on commit 3c60ea7

Please sign in to comment.