Drawing lessons from fatal SELinux bug #1054350
awilliam at redhat.com
Fri Jan 24 17:42:28 UTC 2014
On Fri, 2014-01-24 at 13:36 +0100, Kevin Kofler wrote:
> Adam Williamson wrote:
> > TBH this has always been the one of Kevin's Big Book Of Update Policy
> > Complaints I find the most baffling. If we know you managed to screw up
> > your update once, why exactly would we just trust you to get it right
> > the *second* time without any testing?
> * If the package is already so screwed that it breaks the whole system, it
> cannot realistically get any worse.
Sure it can. It can wipe all your data, or mail it to the NSA...
"Breaks the whole system" is high on the Pantscon Scale, sure, but it's
not the highest. Data loss and security compromise both come higher.
> * A regression fix is usually a trivial change, often reverting something to
> a previous, already well-tested, state.
Sure. And what could possibly go wrong.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
More information about the devel