Il 25/08/2024 08:27, Gioele Barabucci ha scritto:
On 25/08/24 01:46, gregor herrmann wrote: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.)This is why "tag2upload once pipeline passes" is needed. (And more runners.)
Actually I push keeping "UNRELEASED" even in cases where is near sure to be ready because I want see salsa CI result and do fixes/improvements if needed before release, shortly after in major of case I did a release commit with only finalize the d/changelog and I skip salsa CI on that (with "-o ci.skip" on git push) to avoid waste salsa CI resource for same result of the previous.
Will tag2upload be usable in that case (with CI skipped on latest commit with only finalize of d/changelog, and successfull of the previous) or will there be a need for salsa CI successfully completedon the specific release commit?
OpenPGP_signature.asc
Description: OpenPGP digital signature
