Hi, folks!
There's been substantial churn in F19 lately, but from some smoke testing, Final TC5 looks like a basically working build that includes most of the major change we need for final. At this point, 10 days before go/no-go, we really need to do all the desktop validation testing and pin down any showstopper issues that remain.
If folks could grab the TC5 Live images from here:
https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Live/ (KDE, GNOME) https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Spins/ (others)
and help us to fill out the tests at https://fedoraproject.org/wiki/Test_Results:Fedora_19_Final_TC5_Desktop , it'd be a really big help. Just run any of the tests you can for your desktop, file bugs on any failures you hit, and mark your results in the tables according to the key. It'd be especially good to have help with the deceptively large test case https://fedoraproject.org/wiki/QA:Testcase_desktop_menus , which is basically 'run every app installed by default and make sure it works'. If you do hit problems with any of the tests, first check at https://qa.fedoraproject.org/blockerbugs/milestone/19/final/buglist to see if they've been reported as blocker or freeze exception bugs already.
If you hit a serious new failure of a test on KDE or GNOME, mark the bug as blocking the bug 'FinalBlocker' (ideally with reference to a criterion at https://fedoraproject.org/wiki/Fedora_19_Final_Release_Criteria , but if you're not good at criteria ju-jitsu that's OK), or use the blocker proposal web app - https://qa.fedoraproject.org/blockerbugs/propose_bug - to propose it as a blocker. If you hit serious failure of a test on any of the other desktops, mark the bug as blocking the bug 'FinalFreezeException', or use the webapp to propose it as a freeze exception issue.
I have tested that at least each image can boot to a desktop and run the installer; none of them is entirely DOA. Note, testing in virtualization, you *may* run into https://bugzilla.redhat.com/show_bug.cgi?id=974198 ; if so, passing 'nomodeset' should work around it for now.
If you get lost or confused by the process at any point, but you think you've found an important issue, don't hesitate to holler at me or anyone else in QA or release engineering, on list, by direct mail or on IRC. Thanks!