On Sun, Jan 26, 2025 at 10:40:09AM -0500, Stephen Gallagher wrote: > > It's possible that I'm in the minority here, but I honestly don't think > anything should be pushed to dist-git unless it's intended to be built more > or less immediately. Yes, even changes without an immediate functional > impact like the SPDX changes. > > That said, I agree with Kevin that we should have the compose reports list > anything in the compose whose state is "The commit at the HEAD of the > `rawhide` branch does not match the commit used for the latest build in > Rawhide" and treat that as a bug (ideally, we'd open one automatically) I don't think we should be that aggressive on it. It often happens that you need to rebuild things in a side tag and have to coordinate with other maintainers about it, so instantly filing a bug would be kinda anoying, especially if there already is one. > that must be resolved prior to the next mass-rebuild (either by getting a > build done or tagging the bug in some way that indicates that it's okay for > the mass-rebuild to build it). Anything still on the list when the > mass-rebuild is ready to start should be skipped and the bug should be > marked as a blocker for Beta (to make sure it gets looked at). Detecting > this should be fairly easy, albeit adding a bit to the Koji API load. Well, that would need a new Beta critera I guess? I'm not sure blocking beta on some random package not being rebuilt is a good idea. Anything that actually doesn't _work_ should be caught by testing no? kevin -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
