Timeline for Posting warnings about bugs
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5, 2016 at 21:08 | comment | added | HBruijn Mod | +1 for not allowing announcements as stand-alone items. There are indeed other and better channels for that. Having said that quite a few security incidents (get a cute name, their own vanity domains and associated websites and) result in relevant on-topic Q&A's anyhow as people struggle with work-arounds and mitigating measures I.e. BEAST , heartbleed , poodle etc. | |
| Jul 5, 2016 at 13:09 | comment | added | Sam Erde | I haven't used the chat rooms much and don't know how often they are used, but maybe that could be a fitting place to announce defects and vulnerabilities. | |
| Jul 3, 2016 at 18:35 | comment | added | DavisNT | I believe this could be formulated as question/answer. And serious software bugs will create many on-topic questions here (as the users will post questions about situations caused by the bug). In this case software authors have withdrawn the affected release (so there is much lesser need for sharing this info). | |
| Jul 3, 2016 at 18:31 | vote | accept | DavisNT | ||
| Jul 3, 2016 at 18:18 | history | answered | EEAAMod | CC BY-SA 3.0 |