Sorry I've taken forever to get back to you, it's been a busy month.

That said, I have been thinking about this occasionally since you filed it.  Can I ask why you want to differentiate between canary and dev?  It's not immediately clear to me and I think understanding the use case would help.  I kind of am tempted to add a second column which is "Latest Release" which would then show dev (or beta or stable, if they'd been shipped).  That said, that means adding channel name to existing column and then a new column of the same size - maybe not the end of the world (esp. seeing how much whitespace is in your screenshot) but not something I love offhand.

Sorry I could've made that clearer. When looking at this commit list I'm often interested in which of my changes have made it to Dev and which ones have made it to Canary.

In the example screenshot I know that all of these releases are at least in Canary or they wouldn't have a release version, but I don't see which ones have made it into Dev without going to omahaproxy and seeing what the current Dev version is.

Have you clicked into a commit to see details, where it shows canary / dev / beta / stable deployments?  E.g. here is a CL with both canary / dev (https://chromiumdash.appspot.com/commit/bbcce752dbe0afe0913000e7726267564bde7abf) and here's a CL with canary / dev / beta (https://chromiumdash.appspot.com/commit/25dfe9c1d77b4c003bf1282cf83d505aa54f0216).

If the issue is just that clicking adds an extra step, I get that - just want to understand a bit better.  Thanks again for the details, appreciate it.

Ooh, I've never considered clicking on a commit (they don't look clickable to me, and the version number which I'm more interested in is not clickable). That has all the info I want but I didn't know to go there.

I'd still like it to be visible in the commits list but it's less of a concern personally for me now as I know I can get to it.

No longer on the Chrome team, e-mail me @google.com if any attention still required from me here, otherwise good luck!

Updating status to Available, which is the same as Unassigned. Unassigned is an unsupported status type in crbug.com.