diff --git a/release-team/role-handbooks/communications/README.md b/release-team/role-handbooks/communications/README.md index 4a2c5ec3eb9..95e2e2beb79 100644 --- a/release-team/role-handbooks/communications/README.md +++ b/release-team/role-handbooks/communications/README.md @@ -107,6 +107,12 @@ The release lead will drive the content for the release theme and logo. 3. In a second PR opened (ideally) a week before the release day, the Comms Lead will: - remove the `draft: true` parameter - ensure the date parameter is set to the release date +- add the `release_announcement` parameter: + + ```yaml + release_announcement: + minor_version: "." + ``` - add the release logo and theme to the final release blog > [!IMPORTANT] diff --git a/release-team/role-handbooks/communications/templates/release-blog.md b/release-team/role-handbooks/communications/templates/release-blog.md index 33cfe22107f..edf1e1abf64 100644 --- a/release-team/role-handbooks/communications/templates/release-blog.md +++ b/release-team/role-handbooks/communications/templates/release-blog.md @@ -61,11 +61,13 @@ The template should give you some boilerplate. However, each release has its own ```md --- layout: blog -title: 'Kubernetes 1.XX: ' +title: 'Kubernetes v1.XX: ' date: 202n-mm-dd -slug: kubernetes-1-XX-release-announcement +slug: kubernetes-v1-XX-release-announcement author: > [Kubernetes v1.XX Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.XX/release-team.md) +release_announcement: + minor_version: "1.XX" --- --- @@ -207,4 +209,4 @@ Thank you for your continued feedback and support. - Share your Kubernetes [story](https://docs.google.com/a/linuxfoundation.org/forms/d/e/1FAIpQLScuI7Ye3VQHQTwBASrgkjQDSS5TP0g3AXfFhwSM9YpHgxRKFA/viewform) - Read more about what’s happening with Kubernetes on the [blog](https://kubernetes.io/blog/) - Learn more about the [Kubernetes Release Team](https://github.com/kubernetes/sig-release/tree/master/release-team) -``` \ No newline at end of file +```