cc @mraleph.

Before we start testing on more browser maybe we should update the status files for the exiting ones so that we can move that to the main waterfall:
http://build.chromium.org/p/client.dart.fyi/builders/dart2js-safari-mac10.8

At the same time it would be great if somebody would update the status files for the chrome on android bots so that we can move that, it has been on fyi for a number of weeks now.

Additionally, if we test nightly builds what do you propose as an update mechanism?
Auto pull -> bots go red on random commits
Manual update -> better, but requires manual work on a regular basis

I was thinking manual update, but we could add a level of indirection and commit the binary to our repo.

Moving to infrastructure area, setting to low priority for now (we have more pressing issues)

Set owner to @mkustermann.
Removed Priority-Unassigned, Area-Test labels.
Added Priority-Low, Area-infrastructure labels.

Removed the owner.
Added label.

Added Triaged label.

Removed Area-infrastructure label.
Added Area-Infrastructure label.