Priority of issues
Description
Regressions are important. We should not focus on new things unless old ones are working correctly. But is it always true? Is our definition of regression strict enough to allow us go blindly with this process?
The ~regression label is not a priority label. Only ~Deliverable, ~Stretch and ~"Next Patch Release" are.
So, even if we all agree that regressions are important and should be addressed as soon as possible, the process should state that the prioritization is always done, and case by case exceptions are allowed.
Original description
In https://gitlab.com/gitlab-org/gitlab-ce/issues/37406#note_39288217 the point was raised whether regressions always have higher priority than deliverables (in that case specifically for frontend). From my experience that is the process (even though we couldn't find it documented) but we don't follow the process lately.