# ¿Notificación sobre correcciones críticas de errores? **URL:** \ **Category:** Product Support\ **Created:** [21 Marzo, 2019 08:13 UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224 "2019-03-21T08:13:08Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![terraboss](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/terraboss/32/579307_2.png) [@terraboss](https://meta.discourse.org/u/terraboss)\ **Post date:** [21 Marzo, 2019 10:54 UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/6 "2019-03-21T10:54:17Z")
> [@codinghorror](#): > > This tag SECURITY already exists (read our security.md file in the github repository if you don’t believe me), so you’re asking for something that is already there… Thanks for the hint! Can’t remember to see that before at the Github commits page.I’ll keep my eyes more open in future 🙂 **Definition of „Critical“:** I‘d like to cover situations of potential risks (= probability x amount of danger) for user data and system / security integrity. The threshold should be defined by security experts in your team, with a good understanding of [FMEA](https://en.m.wikipedia.org/wiki/Failure_mode_and_effects_analysis) at Discourse. More general: It’s nessary to categorize “unwanted effects” in terms of quality management. Unfortunately, quality management never was and will be a popular topic due to the extra classification and documentation work. But I think, any QM is better than none. Or did I miss something at the agile development culture of Discourse? 🤭🤔 --- _[View the full topic](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224)._