Regular LTS releases have previously aligned to DPDK main branch releases so that fixes being backported have already gone through DPDK main branch release validation.
Now that DPDK main branch has moved to 3 releases per year, the LTS releases should continue to align with it and follow a similar release cadence. Update stable docs to reflect this. Signed-off-by: Kevin Traynor <ktray...@redhat.com> --- doc/guides/contributing/stable.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst index 69d8312b47..9ee7b4b7cc 100644 --- a/doc/guides/contributing/stable.rst +++ b/doc/guides/contributing/stable.rst @@ -39,5 +39,5 @@ A Stable Release is used to backport fixes from an ``N`` release back to an ``N-1`` release, for example, from 16.11 to 16.07. -The duration of a stable is one complete release cycle (3 months). It can be +The duration of a stable is one complete release cycle (4 months). It can be longer, up to 1 year, if a maintainer continues to support the stable branch, or if users supply backported fixes, however the explicit commitment should be @@ -62,6 +62,8 @@ A LTS release may align with the declaration of a new major ABI version, please read the :doc:`abi_policy` for more information. -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 +It is anticipated that there will be at least 3 releases per year of the LTS +or approximately 1 every 4 months. This is done to align with the DPDK main +branch releases so that fixes have already gone through validation as part of +the DPDK main branch release validation. However, the cadence can be shorter or longer depending on the number and criticality of the backported fixes. Releases should be coordinated with the validation engineers to ensure -- 2.31.1
