On Sun, Jan 26, 2025 at 6:26 PM Björn Persson <Bjorn@rombobjörn.se> wrote: > If I correct a typo in a comment, I should bump the release and cause > churn on build servers and mirrors, even though nothing at all changes > in the binary package? I do worry about server/storage usage, but in my more innocent years I have made a change to a comment (which included a new type of typo error) and that resulted in build breakage. I learned that even a small (of what I thought was an) innocuous change might itself cause issues, and learned that just adding building to every change was the safest way forward. Those that never make typos when fixing the typos they first typed probably do not have the same experience or concerns. If you are worried about storage usage on mirrors, a scratch build at least strongly suggests that the package will likely build in the next (mass) rebuild. CI can mean different things to different organizations, but building on every commit can certainly be useful to catch some issues early. I think I have previously suggested that every push should (by default) trigger a scratch-build (with overrides for full build or no build for packages/packagers with special needs), so that the project is less likely to have surprises much later in the process. Identifying the push but no build case in a different way can also work. -- _______________________________________________ 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
