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 <josh@hoblitt.com>
(cherry picked from commit 9e35153876)
This commit is contained in:
1 parent
45a7bbff9d
commit
c07df321a0
1 file changed
+5
@@ -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.
|
||||
|
||||
|
||||
Reference in new issue
Block a user