Release Manager (RM) Role Description
esc edited this page Aug 10, 2023
·
1 revision
-
The RM is accountable for the release but can delegate responsibility to the co-RM (or anyone else)
-
Ensure that the co-RM is informed when RM is AFK
-
Two phases:
- Development phase
- Publication phase
-
During Development Phase
- Negotiate with FPOC to assign reviews and add items to the backlog
- Own the milestones
- Check on their state daily
- Update them based on status
- Hold backlog curation meetings as appropriate to increae/decrease the size of the backlog
- Report on the status/burndown of the release during triage and public meetings
- Run the merge-party, report the current CI weather (Build Farm and Azure) in #numba-fpoc
- Fixup build-farm: restart workers and cleran disk space when needed
- Keep an eye on
main
builds and triage any failures, either revert or delete finding a solution - Prep the meeting notes for each week using the script at:
- Upload the meeting notes to the wiki using the script at:
-
During Publication Phase
- Create and own release checklist
- Run the publication of the release
- Gather feedback from community, ping important parties