diff mbox series

[2/2] doc: update LTS release cadence

Message ID 20211213164858.74244-2-ktraynor@redhat.com (mailing list archive)
State Accepted, archived
Delegated to: Thomas Monjalon
Headers show
Series [1/2] maintainers: fix stable maintainers list | expand

Checks

Context Check Description
ci/iol-aarch64-compile-testing success Testing PASS
ci/iol-x86_64-compile-testing success Testing PASS
ci/iol-intel-Performance fail Performance Testing issues
ci/iol-aarch64-unit-testing success Testing PASS
ci/iol-intel-Functional success Functional Testing PASS
ci/iol-x86_64-unit-testing success Testing PASS
ci/iol-broadcom-Functional success Functional Testing PASS
ci/iol-broadcom-Performance success Performance Testing PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/github-robot: build success github build: passed
ci/intel-Testing success Testing PASS
ci/Intel-compilation success Compilation OK
ci/checkpatch success coding style OK

Commit Message

Kevin Traynor Dec. 13, 2021, 4:48 p.m. UTC
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 <ktraynor@redhat.com>
---
 doc/guides/contributing/stable.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

Comments

Thomas Monjalon Jan. 11, 2022, 4:53 p.m. UTC | #1
13/12/2021 17:48, Kevin Traynor:
> 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 <ktraynor@redhat.com>

Series applied, thanks.
diff mbox series

Patch

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