On Wed, Jun 22, 2022 at 06:18:08PM -0700, Adam Williamson wrote: > On Thu, 2022-06-09 at 12:48 -0700, Adam Williamson wrote: > > Hi folks! > ... > > I think doing this could really help us keep Rawhide solid and avoid > > introducing major compose-breaking bugs, at minimal cost. But it's a > > significant change and I wanted to see what folks think. In particular, > > if you find the existing gating of updates for stable/branched releases > > to cause problems in any way, I'd love to hear about it. > > > > Thanks folks! > > One thing I forgot to mention in the original email, the benefit here > isn't theoretical - I've already caught several Rawhide-breaking bugs > early, or been able to identify the cause more easily, because we have > the tests running in staging. Here's an example I just caught: a new > popt version that was sent out today seems to break authselect, which > is a critical problem and breaks all new installs: > > https://bugzilla.redhat.com/show_bug.cgi?id=2100287 > > if nirik catches my message in time before the next compose runs, he'll > be able to untag the new build and the compose won't be completely > broken. If we had this testing deployed in prod and gating turned on, > the update would be blocked automatically. It's been untagged from rawhide and eln. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-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/desktop@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
