On Wed, Sep 21, 2022 at 12:42 PM Vít Ondruch <vondruch@xxxxxxxxxx> wrote:
I have just reported this against mutter:
https://bugzilla.redhat.com/show_bug.cgi?id=2128660
This was reported upstream a while ago upstream and there are fixes
since yesterday. Not sure if it qualifies as a blocker and how to mark
it for a review ...
Thanks! I'm happy to help get this fix landed downstream, but I'd like the megaupdate to go to stable first.
To mark something as a blocker, there's two ways: a) Go to https://qa.fedoraproject.org/blockerbugs/ , Login, and then click Propose.
b) Directly mark it in bugzilla as blocking the blocker (or Freeze Exception) tracking ticket.
I don't think it's necessary to go through the blocker process in this case since we can just get it fixed before the freezes start, and also because vim that's affected isn't on the Workstation install media so it's unlikely to get accepted as a blocker. What it would qualify as in my opinion is a Freeze Exception, but it doesn't make much sense to propose it as such since we aren't in a freeze yet.
--
Kalev
_______________________________________________ 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
