[Debian-salsa-ci] Can Salsa CI help decrease the number of rejects in NEW?

[Otto Kekäläinen]

Hi!

> > Is anyone from the FTP Masters willing to collaborate on this?
>
> What kind of work do you expect us to do?

I am not sure, I am open to suggestions. Maybe if we have a call and
brainstorm together how checks done by Salsa CI could proactively
prevent rejects, what those checks should be and once they are
technically done have validation that they are correct and meaningful?

> > I don't want to invest time in doing something that is supposed to
> > help the NEW review unless we actually have confirmation and
> > endorsement by FTP masters that this CI job is reporting correct and
> > relevant findings.
>
> Why don't you choose a similar workflow as other teams: upload to NEW,
> check the reason of the REJECT, improve your tools. Do you really expect
> that all packages are checked twice: once after the CI job and second
> when the package reaches NEW?

I am not sure what "other teams" here refer to. Anyway, for
expectations I expect that the person doing the packaging will check
the package multiple times manually and with all tools and CI support
available. If we in Salsa CI could offer more extensive testing/checks
that serve the purposes of NEW review, the FTP Masters would have less
work and the number of REJECTS would be lower and everybody should
benefit.