Suggestion for communication improvement around last auto-deploy branch
Background
For the last few months, we face questions about if there will be a new auto-deploy branch cut on the 18th and whether that new auto-deploy branch will be part of the milestone.
Assumption
Based on #1110 (closed), I am assuming that a new auto-deploy branch is indeed cut on the 18th. It will be part of the milestone subject to the usual caveats (CI green, successfully made it to GitLab.com)
Proposal
This is extracted from #1110 (closed). I would suggest tweaking the message to let people know that the RM is planned to cut a new auto-deploy branch on the 18th
:mega: This is the latest commit running on GitLab.com and this is guaranteed to be released on the 22nd.
https://gitlab.com/gitlab-org/gitlab/commits/SHA
--The stable branch for the release will be created on the 18th (pending weekend).
++Another auto-deploy branch for the release will be created on the 18th (pending weekend). The inclusion of the auto-deploy branch created on the 18th in the release is subject to the usual caveats (CI green, successfully made it to GitLab.com by 20th)