On Wed, 2020-10-28 at 17:21 -0400, Ben Cotton wrote: > I don't blame you one bit here. Part of the issue with this policy is > enforcement. We have to trust maintainers to submit updates that will > meet it (and we should trust our maintainers!), but it can be hard to > tell until it's already in the compose. (In some cases, it's obvious, > but not all). The policy is good guidance, but I don't think it can > reasonably be an enforcement mechanism. The policy I proposed (as an > idea, mind you, not an endorsement) would provide a very heavy-handed > enforcement. > > It also takes the undue burden off of Adam to audit every FE. Many > times, the FE is approved before the fix is available, so it's hard > for voters to weigh in on whether or not the fix is reasonably-sized. One of my trademark nitpick-y process things here: technically speaking, FE status attaches to the *bug*, not the *fix*. A bug having FE status *allows* us to pull a fix for it through the freeze. It does not *require* us to do so. There is a kind of best-judgment filter applied at the push request stage: whoever's doing the push request (so, usually me again :>) can just choose to leave an update out. Whoever's *doing* the push (so, usually mboddu) can also question any item in it, and sometimes we talk them over before I send the request. This bit of the process is a bit 'hidden' because it really only involves two people, but it is pretty much there by design. There are other ways an update that is marked as fixing an FE can get left out, of course. It needs to be submitted for stable to be eligible for the stable push (though not for a candidate compose); negative karma can prevent that. There is a bit of fuzz here in that when the proposed fix for an FE is *already available* or at least roughly envisaged, that can feed into the process of reviewing it. This is, viewed very technically, a process violation, but humans being humans, we do it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx
