Hey folks, just a quick update on what's going on with the F16 release.
So validation of RC2 is looking very good overall. However, we did find a couple of issues that were accepted as blockers at the QA meeting:
https://bugzilla.redhat.com/show_bug.cgi?id=750228 - efidisk.img is broken https://bugzilla.redhat.com/show_bug.cgi?id=651305 - KDE upgrade is broken
We're going to spin an RC3 to fix the second, and a couple of Xfce / LXDE NTH issues, but it shouldn't negate RC2 testing; we'll only really have to sanity check the RC3 images aren't totally broken and re-do the KDE testing, we don't need to re-do the entire installation matrix or anything.
The first bug is rather mysterious; we can't figure out what's causing it. But happily efidisk.img is rather unimportant these days and there's no functional difference between RC1 and RC2 as far as efidisk.img goes, so if RC3's also turns out to be broken, we'll simply ship the RC1 efidisk.img.
The RC2 testing looks to be almost complete, great job everyone! As long as RC3 doesn't explode we should be able to green light the release tomorrow. If anyone's concerned about any bug which doesn't seem to be getting attention, please let me know.
Adam Williamson wrote:
tomorrow. If anyone's concerned about any bug which doesn't seem to be getting attention, please let me know.
I'm wondering about https://bugzilla.redhat.com/show_bug.cgi?id=737430
It may just be a limitation of using GRUB2, but there's nothing in the release notes or common bugs. I would have expected more people to have seen it if it's really an issue.
On Mon, 2011-10-31 at 20:26 -0700, Samuel Sieb wrote:
Adam Williamson wrote:
tomorrow. If anyone's concerned about any bug which doesn't seem to be getting attention, please let me know.
I'm wondering about https://bugzilla.redhat.com/show_bug.cgi?id=737430
It may just be a limitation of using GRUB2, but there's nothing in the release notes or common bugs. I would have expected more people to have seen it if it's really an issue.
It's mostly fixed in final. Custom partitioning pops up the 'disk select' screen now so you can pick the bootloader target disk earlier on in install. I think you can hit it on the upgrade path somehow, but that's about all.
I'll mark your report a dupe of the bug where we fixed it, even though that one's newer.