It's been a focused day of knocking down beta release blockers, in which I think we've all learned the value of marking bugs appropriately and in a timely fashion (especially ensuring that we don't scope creep bugs; there's plenty of room left in Bugzilla, always feel free to file a follow-up!) and regression hunting.
Here's where we stand:
https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0:beta5
bug 586837 is a release engineering dry-run, and we can move to builds without it
bug 592125 is a blocklist update which should resolve bug 591880 and bug 591678
bug 591671 will be solved by bug 579323 which has a reviewed patch and is landing soon
bug 589529 has a fix which will land (though at the cost of breaking a11y support :( )
That just leaves bug 591879 which is a new crasher since the e10s code landed. At this point we have no leads and no ideas. I am very tempted to unblock on it, as it's not a really frequent crasher, and might do so. If someone could help narrow the regression window, that would be great.
I'll keep you informed, but it looks like we may be done with this freeze by later tonight.
cheers,
mike