Having been heavily involved in product issues over the years what I can say is no one method works for all, forums, emails or de notification, any solution needs to be a combination on all.
I2C Bug has largely gone under the radar In the wider community .
Imo there needs to be a way to get this info out and relaying on people reading release notes or Git is not enough.
There needs to be an approach that covered all aspects of the user base such as
• ArduPilot safety registration scheme, upon downloading with GS software or on website user prompted to register for critical updates to create dedicated list for notification of critical issues.
•Email to registered members of this group.
•Prominent forum/Social media posts like has been done already
• Software identification and notification on connection to Gs and warning.
•Cross posting on non owned/partnered forums
• Prominent Docs and release Norse’s on high lighting the issue in the Wiki and here. A release notes section perhaps.
Much of this can be and has to be driven by the community but also needs process framework in place for it to follow as each issues arises as it con not be relied open for people to go looking for issues.