On 10/10/16 11:57 AM, Jonathan Griffin wrote: > We may implement these wireframes for non-sheriffs, or on a per-user basis, > or only for Try.
Thinking in terms of "developers look at single pushes on try, sheriffs look at multiple pushes on non-try" is wrong on all four counts. Many of the developer bugs filed on treeherder are because they keep open an "&author=" tab showing several of their try pushes at once; I push to try quite a bit, as do other sheriffs; I also sometimes look at single pushes on other trees (generally for the same thing a developer, or I, am looking for while looking at a try push: is everything on this particular push done and good, so I can send this push to its next destination?); any developer who never looks at the results of their pushes anywhere other than try is just throwing themselves completely on the mercy of sheriffs, not a group widely known for mercy. Instead what we should be doing is developing a great single-push view, which might include some (though certainly not all, widely separating failures from passes of the same job is horrifying) of the features in those mockups. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
