# Notification about critical bug fixes?

**URL:** https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224
**Category:** Support
**Created:** [March 21, 2019, 8:13am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224 "2019-03-21T08:13:08Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![terraboss](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/terraboss/32/381157_2.png) [@terraboss](https://meta.discourse.org/u/terraboss)
#### Post date: [March 21, 2019, 8:13am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/1 "2019-03-21T08:13:08Z")

</div>

Hi friends,  
did you know these moments?: You’ve installed a bunch of bug fixes with the 1-click-updater and at the next days, you’ll notice even more bug fixes. It’s great to have a classification of features and fixes..

But how about an additional tag like e.g. [urgent] and [security]?

Maybe with a trigger at the Discourse installation itselfs, that notifies the admin about important updates and not just version bumps.

What’s you opinion on that?  
Are there [updates, that could risk data base content](https://meta.discourse.org/t/uploaded-files-mysteriously-going-missing/53361/13), until they are not fixed?

Best

> **I have some bad experience and trouble until now with missing uploads ...**
>
> ![09](https://global.discourse-cdn.com/meta/original/3X/2/6/26c8af05ef042d25e3d93ed7d4d52c8ac62a8fc1.png)

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 21, 2019, 10:12am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/2 "2019-03-21T10:12:37Z")

</div>

When there are updates that are considered urgent they bump the version number.

---

<div class="post-metadata">

### Author: ![terraboss](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/terraboss/32/381157_2.png) [@terraboss](https://meta.discourse.org/u/terraboss)
#### Post date: [March 21, 2019, 10:33am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/3 "2019-03-21T10:33:06Z")

</div>

@pfaffman And you’re suggesting to always wait?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [March 21, 2019, 10:35am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/4 "2019-03-21T10:35:27Z")

</div>

> [@terraboss](#):
>
> [security]?

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.. also I’m not sure what you mean by “critical”. Define “critical” for us all, please?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 21, 2019, 10:36am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/5 "2019-03-21T10:36:04Z")

</div>

Unless you are experiencing a particular issue that encourages you to update sooner. Things do happen between beta releases, but for the most part if there are significant reasons to upgrade they bump the version number.

---

<div class="post-metadata">

### Author: ![terraboss](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/terraboss/32/381157_2.png) [@terraboss](https://meta.discourse.org/u/terraboss)
#### Post date: [March 21, 2019, 10:54am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/6 "2019-03-21T10:54:17Z")

</div>

> [@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? 🤭🤔

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 21, 2019, 10:58am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/7 "2019-03-21T10:58:11Z")

</div>

Oh, and now that you mention it, I do use [Email me Discourse security updates from RSS feed - IFTTT](https://ifttt.com/applets/QtjyYbmD-discourse-security-alerts)

---

<div class="post-metadata">

### Author: ![terraboss](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/terraboss/32/381157_2.png) [@terraboss](https://meta.discourse.org/u/terraboss)
#### Post date: [March 21, 2019, 11:00am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/8 "2019-03-21T11:00:31Z")

</div>

That’s great! Thank you ❤ I need to setup IFTTT again…

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [April 20, 2019, 11:05am UTC](https://meta.discourse.org/t/notification-about-critical-bug-fixes/112224/9 "2019-04-20T11:05:53Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
