Hey, Daniel, please don't sound as if I had questioned the whole workflow for your great work with triaging desktop bugs. It was certainly not my intention to do that; my apologies if it sounded otherwise.
What I brought up was that tag - and the way you said in comment #3 you use it occasionally. In summary, what I want to say is simply: Use that strategy with caution. As regards the possible approach I mentioned, let's take bug #1913222 as an example (with the same bug reporter as this one). - Upstream in nature (and reported upstream) - Low importance - Very unlikely to be patched in Ubuntu - "groovy" tag even if the behavior is not specific to groovy That combo makes me think that "won't fix" would be a proper status right now. I don't see how it's useful to keep it open in Ubuntu's bug tracker for a few months, and then close it in July due to EOL (which would be a reason hard to understand for the bug reporter, who will most likely see the same thing in hirsute). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913218 Title: Obscure shortcut selector behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1913218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
