Create notification for release post items merged into master post content assembly
Background
Locking directories during the release post assembly process has been causing issues over the last several releases for other team members in getting out important changes to prod. More details here: gitlab-org/gitlab#301352 (closed)
Goal
To address, we propose removing the locking steps and, instead, creating a notification (via Danger) that would alert Release Post Leads in the X-Y-Release-Post-Prep
slack room when content is added to the unreleased
folder on master
between the 18th and 22nd of each month.
If the RPM sees a notification, they will then know that they need to work with the appropriate PM to get content in as per post assembly instructions.
Exit Criteria
- [ ] Notification sending alerts to the X-Y-Release-Post-Prep
slack room
-
The @gl-release-post-group
is mentioned in any MRs that include changes to the unreleased directory -
Remove instructions around locking unreleased dir (currently strikethrough !76259 (comment 521503601)) -
Add instructions on how RPMs should deal with a notification -
Add instructions on adding/removing users from @gl-release-post-team
by an Owner through this link based on scheduling
Edited by Phil Calder