Skip to content

Double check Pick into Stable MRs for incorrect milestone

Michael Kozono requested to merge mk-double-check-pick-into-stable into master

The description for ~"Pick into Stable" is:

Merge requests that should be cherry-picked into the ongoing release

The description for ~"Pick into Backports" is:

Merge requests that should be cherry-picked into previous releases

Assuming this is true, then this MR makes sense. In fact, perhaps we could get rid of the milestone filter on the regular link, and not add this checkbox.

But currently, ~"Pick into Stable" is being used as a catch-all. I think this is because ~"Pick into Backports" was added relatively recently.

I proposed in Slack that we relabel MRs to match these definitions

Why

An MR was missed that should have been picked into the current release because it was set to the previous milestone. https://gitlab.slack.com/archives/C0XM5UU6B/p1509400127000337

Merge request reports