Joe Medley

Here's a second example. A feature cannot be both in a dev trial and enabled by default at the same time, but the form allows this and the rendered card...

cc: @jrobbins

I'm not sure this is relevant any more. Spec links are available on both versions of the card.

If it is the iOS field, notice that the form label says it is 'rare'. I curled features.json just now and found there is currently no instance of _any_ iOS...

The sending part is still done by cutting and pasting. This feels somewhat related to "O: We have improved collaboration support for API owners". Adding the ability for Chrome Status...

cc: @PaulKinlan

A related ticket for a deprecation/removal was [marked fixed this week](https://bugs.chromium.org/p/chromium/issues/detail?id=1062400#c20) (even though the removal was [shipped in 89](https://storage.googleapis.com/chromium-find-releases-static/904.html#9044170ea1ff06388da8ce751bc2fb877aacef2f)). As stated above, the deprecation was technically an enabled state. This...

Here's another example of the kind of mess we have now. What it shows is that the owner of this feature didn't know to create a new status entry. 

This is a good place to put this. We need to review the whole way that Chrome Status handles these. We hav some design work to do and we need...

Why were you uncertain that 'Feature deprecation' was the proper feature type. I can't propose an improvement if I don't know what it was that threw you off.