Github labels for upgrade dealbreaker regressions

Development
1

Can we have a Github label (e.g. regression-25.11) for issues that are likely dealbreakers for people upgrading to a specific release, so that people can more easily check if the upgrade will break their system?

For example for the 25.11 release, I found the following regressions that would likely break my workflow and waste time:

Future release upgrade instructions could then also recommend to check that label before upgrading.

Note we already have label 0.kind: regression but that does not allow users to filter for the release they are looking to upgrade to.

4 Likes
2

I went ahead and created a Github project Regressions 25.11.

Please anybody be invited to assign any regressions you find to it.

(Still figuring out how to best configure that project board to make it useful. I’m thinking perhaps we should categorise them as “has workaround”, “fix merged”, etc).

2 Likes
3

(Sorry, creating a new Project was easier then expected and while trying to close my own i accidentally hit the wrong row (your project) in the overview. Didn’t mean to do that.)

4

It’s kinda orthogonal to what you suggested but this made me think of a similar request, to track per-release “stateVersion” changes. It’s already tracked down in the release notes but seeing those through the UI might be nice (but it will add more labels, which could not scale well)