I'm looking for things to do during code freeze, and my regressions list is rather unhelpful. There's a reason each of those aren't fixed yet.
So I thought I'd try organizing the list by component instead. To do this, I wrote a script that would search for open bugs with a regression sha1, grab the sha1, get the description and affected paths from git, and write out a tree.
This turned out to be equally helpful for me, but maybe it'd be useful to someone else? Here it is, just in case.
Maybe I'll try to fix some tests instead.