Reminder bot via triage-ops or Slackbot
Rather than manually sending release post item due date reminders, a ProdOps Slackbot could send the messages on defined dates.
Related issues:
MRs:
!683 (merged)
Messages to schedule-
Opening tasks #14
:bell: REMINDER :bell:
@product-team - All content blocks (features, recurring, bugs, etc.) should be drafted and under review by the 10th. All direction items and notable community contributions should be included in the release post.
cc:
@Farnoosh
-
Initial reminders 1
@product-team 📣 Release post reminders 📣
1. Today is the day to have your release post items created and in review by your PMM and TW counterparts.
2. Please follow the [file naming guidelines](https://about.gitlab.com/handbook/marketing/blog/release-posts/#instructions) as it affects the release post template as well as the release post team's ability to find release post items with ease.
3. Please work with your EM to add high-impact bugs to the [release-x-y-bugs MR](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/117274)
4. Please work with your Product Designers to highlight significant usability improvements in the [release-x-y-usability-improvements MR](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/117275)
cc: @fseifoddini @brhea
-
Initial reminders 2
Please ensure your bug fixes and performance improvement issues are [appropriately labeled for inclusion in the release post](https://about.gitlab.com/handbook/marketing/blog/release-posts/#usability-improvements-performance-improvements-and-bug-fixes).
(We no longer link to a curated list of bugs, performance, and UX improvements in the release post. As of 15.9, [we link to a filtered list of issues for each milestone](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/118569).)
cc: @fseifoddini @brhea
-
Initial reminders 3
Please ensure your usability improvement issues are [appropriately labeled for inclusion in the release post](https://about.gitlab.com/handbook/marketing/blog/release-posts/#usability-improvements-performance-improvements-and-bug-fixes).
(We no longer link to a curated list of bugs, performance, and UX improvements in the release post. As of 15.9, [we link to a filtered list of issues for each milestone](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/118569).)
cc: @fseifoddini @brhea
-
Various tasks and followups due by the 15th
In the `#release-post` channel remind all PMs that have their release post item MRs merged by EOD on the 17th or bump the milestone if they know it won't make it.
-
On the 17th
In the `#release-post` channel remind all PMs that it's the 17th, so they need to either have their EMs merge their release post item MRs or bump the milestone if they know it won't make it.
-
Generate Deps and Rems
Ping Product Operations `@brhea` to [generate the deprecations and removals indexes]
-
Content Assembly
@product-team 📣 Content assembly 📣
1. Content assembly will happen via automation on the 18th at 4 pm UTC (11 am ET / 8 am PT).
1. Any un-merged MRs after that time should no longer target `master`.
1. Follow the steps here if you need to merge your items after the automation has run: `https://about.gitlab.com/handbook/marketing/blog/release-posts/#adding-editing-or-removing-merged-content-blocks-after-the-18th-and-before-the-22nd`
cc: @fseifoddini @brhea
-
20th final check
On the 20th, ping Product Operations DRI (`@fseifoddini` ) for final check in the `#release-post` channel
Edited by Brian Rhea