We should have an agent to continue drive backports in projects we care about (target version != desired backport version).
Either via cherry-pick bot commands (+ a bunch of retesting) or via fixing conflicts automatically.
That agent should monitor pass rates in sippy too, so we can be sure that after some soak period it is safe to merge the next release branch with it.
We should have an agent to continue drive backports in projects we care about (target version != desired backport version).
Either via cherry-pick bot commands (+ a bunch of retesting) or via fixing conflicts automatically.
That agent should monitor pass rates in sippy too, so we can be sure that after some soak period it is safe to merge the next release branch with it.