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 develo
the name of the patch
author. Sheriff has always to check if they are different when a patch
has issues and the developer has to be pinged on IRC. Suggestion:
Highlight when patch author is different from pusher.
- It's still possible to select multiple trees. Do people use this or
makes it se
On 10/10/16 2:57 PM, Jonathan Griffin wrote:
https://drive.google.com/file/d/0B3__-vbLGlRHajhEOE1SVXBQUU0/view?usp=sharing
Just to check, were these wireframes tested at window widths around
1000px or so? All the screenshots there are pretty wide, looks like.
Moving the commit info to above
TL;DR - we'd like some feedback on some UI changes to Treeherder
recommended by a 3rd party UX team.
The longer story - a 3rd party UX team has provided us with some
suggestions on how to improve Treeherder's UI from the perspective of the
average developer. They've created a set of wireframes her
4 matches
Mail list logo
