Someone asked in my last post if RC3 was the final version.
The answer is: Nope – we had to do two respins after RC3.
Thursday night we found, filed, debugged, and fixed the fsck-at-boot / rhgb hang at first boot problems (see bugs #357401 and #362721 respectively), completed the fix for #357401 (dmraid+livecd) and then rebuilt all the install and Live images to create RC4 for Friday morning. Friday’s rawhide report notes these changes.
During Friday we found and fixed a bug in selinux-policy-targeted where restorecon etc. would screw up at install time and leave you with SELinux non-functional. Once again Jesse rebuilt all install/Live images – creating RC5 – with this change included. This change is listed in Saturday’s Rawhide Report.
Once the RC5 bits were built (mid-afternoon Friday) we desperately tried to smoketest them and get them rsync’d to the Raleigh office before 9pm so that we could hand them off to the internal IT guys. (After 9, it would be too late to get it done for Monday, and we’d have to delay the release.)
The bits landed at 8:45pm. All our testing showed that the bugs above were, indeed, fixed. Jesse made the call, got a response, and that was that.
There were heroic efforts from a lot of people in those last two days, and I raise my glass to one and all.
oh jeez linux 
where to get RC5?
RC5 == F8 Final
You’ll get it when it’s released: November 8.
Re: RC5 == F8 Final
sniff sniff. I knew you’d say that.. 🙂
Can’t wait, F8 will rock!
Yeeh thanks
Thanks for answering my question in your previous post 🙂 This week we’ll have a new Fedora install fest @ my company I guess 😀
Do I now need to reinstall after RC3?
I just finished installing RC3. Given the bugs fixed above do I need reinstall when F8 is released or will a yum update fix everything?
Re: Do I now need to reinstall after RC3?
You should be fine with a yum update. The first three bugs only affected the first boot for a newly-installed system, and I’m almost sure the SELinux problem only affected RC4.
Just in case, though, you might want to check for SELinux audit messages and/or do a filesystem relabel after you do the yum update.
In all honesty…
Jeremy did all the Live image work. He has handy dandy scripts to churn them out once there is a repo with the right packages in it. I didn’t do it all myself (: