Add release announcement field to the Communications handbook#2987
Add release announcement field to the Communications handbook#2987kfess wants to merge 2 commits into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kfess The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/hold We are in the middle of the cycle for v1.36, and would want to keep the handbook changes to minimum. FYI @chadmcrowell |
|
Sure! Would be great if you could revisit this once the v1.36 release is done. Thanks! |
|
I updated the front matter in the release blog template as well 04159c4 |
What type of PR is this:
/kind documentation
What this PR does / why we need it:
Add documentation for the
release_announcementfield in the release blog frontmatter to the Communications handbook.This field is being introduced in kubernetes/website#54885 to support the automated release series page generation. The release series pages (e.g., /releases/1.35/) will automatically link to the corresponding release announcement blog post using this frontmatter field.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
The release series pages (e.g., https://kubernetes.io/releases/1.35/) are now auto-generated from existing data (kubernetes/website#54041). To automatically display a link to the release blog on these pages, PR (kubernetes/website#54885) is trying to add support for the
release_announcementfield in the blog frontmatter.As suggested in kubernetes/website#54885, this PR updates the handbook so future Comms leads know to add this field.