The important question here is not "How do we fix this bug?" but "How do
we prevent this sort of bug from occurring again?" Please take the time
to read this excellent article about how software is written for NASA's
shuttles, paying close attention to the part about "The Process":
http://www.fastcompany.com/node/28121/print

The Ubuntu team's process failed to stop a major data corruption bug
from being released, even though it was known about ahead of time. I'm
not assigning blame to any one person; we are all affected by the
process. So, what part of the process failed *us*? What needs to change
about the way the way software is released in the Ubuntu project?

-- 
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to