From c07df321a0242d5aef7d0259a6567852fcd414ea Mon Sep 17 00:00:00 2001 From: Joshua Hoblitt Date: Wed, 1 Jul 2026 08:18:20 -0700 Subject: [PATCH] docs: note the support matrix update in the release process Add a step to the release process, when creating a new release branch, to add a row for the new release series to the support matrix in the Maintenance and Support page. This keeps the matrix current as new minor versions are released. Signed-off-by: Joshua Hoblitt (cherry picked from commit 9e351538768f9b60038f20f56bbd426beeb9c564) --- build/release/README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/build/release/README.md b/build/release/README.md index 0e855b3ce..a67b678fd 100644 --- a/build/release/README.md +++ b/build/release/README.md @@ -73,6 +73,11 @@ necessary, and we immediately release `...-beta.0` Create a PR to the new release branch that updates the documentation and example manifests with a beta tag (e.g. `v1.13.0-beta.0`). For example: https://github.com/rook/rook/pull/13308 +As part of that documentation update, add a row for the new release series to the support matrix in +`Documentation/Getting-Started/maintenance-and-support.md`, using the Kubernetes range from +`Documentation/Getting-Started/Prerequisites/prerequisites.md` and the Ceph versions from +`Documentation/Upgrade/ceph-upgrade.md`. + After the PR is merged, you can tag the release with the beta tag (`v1.13.0-beta.0`) following the [Tagging a New Release](#tagging-a-new-release) process below.