And because, after they learned about the problem, they failed to communicate effectively and never removed the cd-image.
This has never happened before, and obviously there was no policy for this situation. Which automatically means that some developpers turn into 'its your fault'-mode and be less supportive of the community members who have bricked their hardware. It turned into a blame game. There were more "it's an alpha .. you knew what you were getting it to " expressions than any compassion. Worse, appearantly its easier to type "it's an alpha .. off course it's going to break your hardware .. and you test on your own risk" .. 10 times .. than to put a warning up. At least: it was said at least 10 times before the warning was up. That speaks volumes about priority. And the image is still available and linked to from many places that do not contain the warning. The mistake was just an oopsie .. the aftermath, how it was being dealt with, (and still is) .. a PR horror. 2008/10/2 Lorenzo Zolfanelli <[EMAIL PROTECTED]> > On Wed, Oct 1, 2008 at 7:46 PM, vjohn <[EMAIL PROTECTED]> wrote: > > > > So, the Intel haven't opened the code of your hardware? So, how it's > > happen? > > > > It's happen because it isn't a stable kernel release, and because linux is > developed by humans, and they might make mistakes. And I think the linux > testing team was to small to reveal this bug. Apologetic. > > > -- > [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at > risk > https://bugs.launchpad.net/bugs/263555 > You received this bug notification because you are a direct subscriber > of the bug. > -- [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk https://bugs.launchpad.net/bugs/263555 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
