Hi!, Does other Release Team members have any thoughts on potentially using the existing vcswatch information for unstable -> testing transitions?
Repeating some suggestions I threw in my first email: > The vcswatch tool is tracking the CI pipeline status on Salsa for all > packages that have a Vcs-Git URL pointing to Salsa. There could be for > example a rule that if a package is hosted on Salsa, and if the git > repo is up-to-date with what was uploaded and CI is passing, the > package could migrate faster from unstable->testing. Alternatively > there could be a negative rule that adds extra delay to any package > that is not in sync in git or has no CI or a failing CI. I guess one > could also justify a ruleset where packages with no CI are considered > neutral, but if there is a CI and it is failing, the package would get > extra delay or not migrate from unstable to testing at all as there is > something that provably regressed. I will reply to Adrian's comments about Salsa CI usage later, but I wanted to ask this first to get the discussion back on topic.
