Hey folks! I figured a wider heads-up about this might be useful. The owner of the "Dropping of cert.pem file" Change[0] committed the change to dist-git but did not build it, instead leaving it to be built as part of the mass rebuild[1]. This, unfortunately, was a really bad idea.
Mass rebuild changes bypass automated testing and gating, and land all at once in a huge lump. This has several consequences if a mass rebuild build breaks things: 1) The change is not gated as it might be if it went through gating, but immediately goes out and breaks real-world cases 2) Unrelated subsequent updates may get gated because tests on them fail due to the change 3) Investigating the breakage is difficult and time-consuming because the 'suspect pool' of packages is *every single package in the mass rebuild* Please, *always*, only land significant changes when you are ready to build and submit them as regular updates. In general, the delta between what is currently in Rawhide and what the mass rebuild will build should be *as small as possible*. Any unbuilt/blocked change sitting in dist-git prior to the mass rebuild is essentially a time bomb. [0] https://fedoraproject.org/wiki/Changes/dropingOfCertPemFile [1] https://bugzilla.redhat.com/show_bug.cgi?id=2360110#c2 -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
