---
# System prepended metadata

title: Comms team improvement notes

---

# Comms team improvement notes

This document is meant to contain improvment ideas/tasks we see as we work through the release of v.1.4.0.

# Tasks
- [ ] Create a release notes template based on something like https://github.com/kubernetes-sigs/cluster-api/releases/tag/v1.3.0. HackMD can import nodes from github.
- [ ] How do we make sure comms team is aware of things like https://github.com/kubernetes-sigs/cluster-api/issues/7486
- [ ] Based on https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#polish-release-notes we need to ensure consistent formatting e.g prefix. We should have a list of prefixes. 
    - [ ] maybe make sure the approvers label the correct prefix
    - [ ] might already be listed in the
- [ ] See if there is a way to run netlify without having to create a PR post release provider-config-example.yaml
- [ ] update release notes so they are always are meaninful points or something they need to know about

# Tasks from [issue 7524](https://github.com/kubernetes-sigs/cluster-api/issues/7524)

- [ ] Define details of "Communicate key dates to the community"
- [ ] Consider adding expandable auto-generated release notes for beta and RC (non-GA) releases
- [ ] Ensure we have documentation on how to consume beta / RC releases (for users)
- [ ] Document how to consume nightly Cluster API releases with clusterctl and with the test framework
- [ ] Potential improvements to generating release notes that automatically have the clusterctl: or E2E: or KCP: against the PR titles. Currently this process is done manually. May be we can improve this my looking at the area/xxx label of the PR or even consider some kind of PR title validation to make sure that users provide the prefix (kind of like how they currently provide ✨ , 🌱 , etc)