Comment 31 for bug 727594

Revision history for this message
Bryce Harrington (bryce) wrote :

> Bryce, the patch is empty...

Ha, true enough. Let's try that again.

Btw, I'm pretty sure the release is already more or less in the bag, so the fix is not likely to make it to the cd. (I could be wrong; it's a severe enough bug the archive team might pull it in if there are other last minute bugs making it worthwhile to regenerate the CD iso.)

It's more likely this will go through the SRU process. That means, it'll be reviewed and approved to go into natty-proposed for people to test, where it'll love for a period from a week to several weeks until enough testing has been done to show it does not cause regression. At that point it will move to natty-updates and be generally available to all users.

If a lot of people test -proposed and give it a +1, that will help accelerate getting the fix into the release. If people test it and find any regressions, that will significantly delay it going in until those issues can be investigated and resolved. So, hopefully lots of people give +1's and no one gives -1's, and we'll see this live for natty for people to update to post-release.