diff --git a/docs/release.md b/docs/release.md index 598eba9e..4e359de0 100644 --- a/docs/release.md +++ b/docs/release.md @@ -49,6 +49,22 @@ This will trigger a [release GitHub action](https://github.com/rancher/turtles/a **Note:** If you are cutting a new minor/major release, please follow the [next step](#post-release-steps-in-rancher-turtles-docs) below, otherwise skip. +## Announcing a release + +When the new release is available, we need to notify a list of Slack channels so users and relevant stakeholders can stay up to date with the latest version and changes: +- SUSE Software Solutions `discuss-rancher-cluster-api` +- SUSE Software Solutions `team-engs-on-rancher-manager` +- Rancher Users `cluster-api` + +You can use the following notification template and adapt it to the specifics of the release you are announcing: + +``` +Hi all! We are happy to announce a new release of Rancher Turtles - vx.x.x! With this release we : +- list of relevant features/fixes +- ... +Please, take a look at the release notes . +``` + ## Post-release steps in Rancher Turtles Docs If a new minor/major branch was created, there are some post-release actions that need to be taken. @@ -130,4 +146,4 @@ The `release-X` branches contain stable, backwards compatible code. On every maj Rancher Turtles maintains the most recent release/releases for all supported APIs. Support for this section refers to the ability to backport and release patch versions; [backport policy](#backporting) is defined above. - The API version is determined from the GroupVersion defined in the top-level `api/` package. -- For the current stable API version (v1alpha1) we support the two most recent minor releases; older minor releases are immediately unsupported when a new major/minor release is available. \ No newline at end of file +- For the current stable API version (v1alpha1) we support the two most recent minor releases; older minor releases are immediately unsupported when a new major/minor release is available.