For comm-central based or mobile based trees, there are multiple repositories that could generate builds. Pushes to the all the relevant repositories need to be displayed and handled in some form. For example, in TBPL it is currently very difficult to tell which m-c changeset has broken Thunderbird without going back and forth selecting builds and then links (to me it is one blocker to be able to switch completely to tbpl as results are attributed incorrectly, or not at all in some no-pushes for a long time cases). I'm not sure what UI I'd suggest, but maybe experimenting with multiple columns for the changesets we should allow for changes to two or three displayed repositories.
Product: Webtools → Tree Management
TBPL has been EOLed (bug 1054977).
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.