Comment 79 for bug 259168

jmcantrell wrote:

> If you're looking for the most rock-solid Ubuntu experience, then you
> should stick with the LTS releases. The last one was Hardy Heron. Using
> the non-LTS releases, you have to understand that they're going to be a
> bit more bleeding edge. At the very least, you should wait to verify
> that packages which are critical to you are not broken before upgrading.

The "fix" for the Hardy Heron kernel freeze is to upgrade to the
Intrepid kernel, or regress to Gutsy. Also the broken mjpeg streaming
in Firefox that will not be fixed until 3.05. My entire enterprise is
frozen a Gutsy right now as it is stable, and Hardy is not. And since
the fixes to the two major bugs for me are version changes, they can not
happen within Hardy.

Which sidesteps the point of how these bugs are surviving through
extensive betas, and 6 months of production. There is a very good
chance that the "fix" for this bug will be regression to Intrepid
network manager, or the next version that can't ship in Intrepid. My
point is that this is getting far too common. I too have been around
since the Badger, and Gutsy BOCH BIOS was the first time I saw this. But
I have been seeing more lately.

And this is way off topic. What is on topic is will there be a fix, a
regression, or a backport type "fix?" And how can we better QC the beta
so that the regression can happen before the freeze?