11.2 follow-up: Use shared pool of merge requests waiting for review
Follow-up from #4 (comment 89706256)
To make review process more flexible we will try using a pool of merge requests waiting for review. If someone has a merge requests needing review/merge, the process will be:
- if developer assigns someone specific for review, nothing changes (workflow is same as now)
- if developer adds label "ready for review" and assigns nobody, this MR can be picked up by anyone willing to review the MR. So anyone interested doing reviews can filter current MRs with "ready for review" label and also mix it with additional label to limit the scope to his expertise area)
- if reviewer picks a MR for review, he assigns himself and removes "ready for review" label
- the same approach can be used for maintainers but with label "review for merge"
TODO:
-
create group labels "ready for review" and "ready for merge" -
create issue board for given labelsmerge request filtered list -
update handbook (probably later only if this approach turns out to be viable and widely used) -
make sure people are aware of this label -
start watching merge requests index page with given labels filter
Edited by Jan Provaznik