release-13-7-bugs
The Release Post Manager will use this template to create separate performance improvement and bug fixes MRs for the release post blog.
Key dates & Review
-
By the 12th, @Release Post Manager
reminds EMs/PMs to draft/submit bugs viadata/release_posts/unreleased/bugs.yml
or performance improvements viadata/release_posts/unreleased/performance_improvements.yml
per release post MR task list item -
By the 15th, @Release Post Manager
assigns MR to TW lead for review and applies labelin review
-
By the 16th: @TW Lead
reviews, applies theready
label and assigns to@Release Post Manager
For this MR, you'll check:
-
The title of the bug, for syntax and clarity. -
The link to the bug report. -
Whether the bug has been closed. - If the bug is closed, was it closed on or before the current milestone?
- If the bug is still open, make sure that the responsible EM, PM, or bug author is aware of the situation.
- If the bug will not be closed by the 20th of the month, remove the entry from the Bugs MR.
-
-
By the 17th: @Release Post Manager
merges the MR, prior to final content assembly
Edited by Michael Karampalas