Comment 8 for bug 392709

What went wrong here? It seems linux-meta 2.6.31.1.11 was uploaded on June 29, 3 days after I reported that kernel 2.6.31-1.13 would not boot on a large class of machines, and giving the exact upstream changelog required to fix the bug. I understand that using versions of Ubuntu that are in the early alpha stage is likely to run into breakage, but how can we fix the process to avoid updating testers to a known-broken kernel with a known fix? Unfortunately a lot of testers' time is going to be wasted by this bug, and also I'm sure a lot of developer time is going to be wasted marking other bugs as dupes of this one.