Hi, ... > I am not saying that Salsa CI is useless for developers when preparing > updates. Whatever tools they use to perform high quality uploads is an > improvment. But that doesn't mean that these tools are a good source for > judging if a package in the archive is ready to migrate to testing.
Again you are purely thinking about individual tests. I wonder if other Release Team members see the forest for the trees? The Release Team is Debian's main guardian of quality. Do you want to reward the diligent people who test their packages continuously or at least once before uploading to unstable, or do you want to maintain a culture where unstable is a playground where anything goes, forcing diligent people to just suck it up and clean up after others? I've seen that the majority of the Release Team members do not use Salsa CI on their own packages and don't want to promote it. However, you could at least enforce a rule that *if* Salsa CI shows a package is broken it should not be ignored and uploaded anyway, preventing the brokenness from spreading from one package to affect multiple ones in Debian unstable.
