On Thu, 22 Aug 2024 00:46:09 -0700, Otto Kekäläinen wrote: > Also, I think a 10-minute break is a good thing for the author > themselves. The maintainer should get some fresh air and do the final > review of their changes after a small break to ensure nothing was done > too hastily.
That depends on the amount, type, and size of packages one is working on. In the Debian perl Group we have 4000 packages, and there are days with 5-10 new upstream releases. Many of the packages are trivial, so updating them (including autopkgtests and blhc and lintian and whatnot) doesn't take longer than 5 minutes. So I can decide to wait for salsa CI for 10 minutes or update 2 more packages in the same time. (Or try to context switch and keep a stack of where I was etc.) I totally see the value of salsa CI for complex packages, for running things which can't be run locally, for merge requests, etc. But there are also situations where it doesn't help. -- I guess what I want to say is that salsa CI is a useful tool, and like every tool, it has its places but it's not a panacea. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `-
signature.asc
Description: Digital Signature
