Discussion: How to ensure release managers have visibility about the patch release pressure?
Context
As part of extending the maintenance policy to backport bug fixes to the last three releases, we will drop the support for the Pick into x.x
label and instead allow maintainers to merge bug fixes into stable branches.
This deprecates the current process used by release managers to determine a sense of urgency patch release: Taking a look at the merged merge requests with Pick into x.x
The ask
Let's use this issue to discuss ideas about how release managers would be able to tell if there's enough pressure to start a patch release. Some questions/ideas to get the conversation started:
- What threshold should be used? Number of merge requests merged, priority of merge requests, etc.
- Should this information be available in the release manager dashboard o have a dashboard on its own?
- Should this be part of the monthly release template? E.g Add a step into the monthly template to review merged MRs every
X
days. - Is there a way to automate this?
- Other ideas?
Update 2022-11-10
A proposal was put together on #2656 (comment 1167047635) and follow up issues were opened #2678 (closed), #2679 (closed)
Edited by Mayra Cabrera