Add a step for ensuring that MRs targeting the stable branches are covered for patch releases
When there are backports, MRs targeting the stable branch because for reasons we cannot take the MRs merged into master, we need to ensure they are picked up as well when we tag a new release.
The automated picker at this time only picks MRs with the pick label that have been merged into master.
I think the thing to do is to add a new step to the template that has the RM double check the following query (11.10 used as an example):
- https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&target_branch=11-10-stable
- https://gitlab.com/gitlab-org/gitlab-ee/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&target_branch=11-10-stable-ee
To ensure there are no "backport MRs" outstanding.
Edited by John Jarvis