@common-issues-triage & people:
Representative example: there is an issue at 5.19.9 with Intel 7265 wireless. 5.19.11 solves the issue and is already in testing (https://bodhi.fedoraproject.org/updates/FEDORA-2022-4def83901c). It will be available in a day or two.
This is, imho, not worth a common issue. On one hand, there is no workaround because Intel 7265 in general does not work with the kernel atm. On the other hand, it was quick to fix on kernel maintainer/team level and 5.19.11 is available in a day or two.
Therefore, shall we use the announcements (which originally is intended for non-technical things) or “ask in English” - maybe with pinning for a day or two for something that might be more widespread? This may avoid several topics and avoid working time (especially as the issue is likely to be fixed with an update before the triage has been finished).
Also, it can help users because it avoids long elaborations in topics for something that cannot be fixed at this level, and it helps to keep the helpers up to date if something like that is going on (so it saves time for them AND the users).
For critical+urgent cases, we might note the bodhi build as “critical case” possibility, adding it as a post or such. However, I suggest to not get used to introduce bodhi builds as official workarounds in a common issue.
What do you think? Pinning announcements? Or pinning a normal “ask in English”? (The latter makes maybe most sense?). Pinning generally, only if assumed to be widespread, or never?
The generally smooth way would be to just add a normal “ask in English” topic without pinning or such, and add the solution once the fix is available in stable. Given that, at least in this case, the issue is not more common/widespread than other hardware-related issues, I tend myself to the smooth way in this case → (Wireless does no longer work since kernel 5.19.9)