Infrastructure improvements for development release maintenance

We have many reports that help us keep track of automatically-detectable problems in the development release (FTBFS, NBS, component-mismatches, the conflict checker, the transition tracker, etc.). These are all well and good, but they are rather disconnected from each other and in many cases do not provide very good facilities for distributing work among developers. If we want to drive these reports consistently to zero, some time spent on infrastructure would be worthwhile. What can we do to improve matters?

2011-11-18 cjwatson: I've dropped the work item to take over and update the weather report, because as explained in the wiki page it seems unlikely that it will be able to simultaneously meet the needs of release management and the +1 maintenance team. I would rather limit the scope and have us do a good job on the latter.