Timeline for Posting warnings about bugs
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2016 at 17:23 | history | tweeted | twitter.com/ServerFault/status/753641063030657024 | ||
| Jul 12, 2016 at 13:04 | comment | added | user | Better still would be, if the update is seriously buggy in a way that risks breaking things for some nontrivial number of people (which is probably why the vendor is working on a fix for the update in the first place), for the vendor to simply pull the update while working on a fix. | |
| Jul 8, 2016 at 0:20 | comment | added | jpaugh | Best etiquette is to disclose the bug to the author/vendor, and give them time to fix it before releasing it publicly. Otherwise, everyone who doesn't read your post might be vulnerable to anyone who does. | |
| Jul 5, 2016 at 21:26 | answer | added | HBruijnMod | timeline score: 4 | |
| Jul 3, 2016 at 19:46 | answer | added | yagmoth555Mod | timeline score: 2 | |
| Jul 3, 2016 at 18:31 | vote | accept | DavisNT | ||
| Jul 3, 2016 at 18:18 | answer | added | EEAAMod | timeline score: 19 | |
| Jul 3, 2016 at 18:14 | history | asked | DavisNT | CC BY-SA 3.0 |