Add "Removed" as an option for the feature's status

[maxh]

Deprecated = planned to be removed
Removed = no longer supported at all

Today we have deprecated but not removed.

[ebidel]

Are there cases where deprecation takes a long time? Right now we're using
Deprecated to mean both Removed and considered for deprecation. My concern
is that the "deprecation grace period" is very short and we're not updating
data quick enough to account for such fine granularity.

On Wed, Mar 12, 2014 at 4:24 PM, Max Heinritz notifications@github.comwrote:

Deprecated = planned to be removed
Removed = no longer supported at all

Today we have deprecated but not removed.

[image: image]https://f.cloud.github.com/assets/1289501/2404537/5ad2f1a0-aa3d-11e3-8fdd-db143d2295f3.png

Reply to this email directly or view it on GitHubhttps://github.com//issues/100
.

[maxh]

The semantic difference between the two has become more meaningful in the
past few months because the number of deprecations and removals has
increased dramatically:

https://docs.google.com/a/chromium.org/spreadsheet/ccc?key=0AjGgk26K1Cc-dHJKNGtlLVlmSGRIYVR3LVRGYnVCRVE&usp=drive_web#gid=0

I think we should account for this.

On Wed, Mar 12, 2014 at 5:01 PM, Eric Bidelman notifications@github.comwrote:

Are there cases where deprecation takes a long time? Right now we're using
Deprecated to mean both Removed and considered for deprecation. My concern
is that the "deprecation grace period" is very short and we're not updating
data quick enough to account for such fine granularity.

On Wed, Mar 12, 2014 at 4:24 PM, Max Heinritz <notifications@github.com

wrote:

Deprecated = planned to be removed
Removed = no longer supported at all

Today we have deprecated but not removed.

[image: image]<
https://f.cloud.github.com/assets/1289501/2404537/5ad2f1a0-aa3d-11e3-8fdd-db143d2295f3.png

Reply to this email directly or view it on GitHub<
https://github.com/GoogleChrome/chromium-dashboard/issues/100>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-37484246
.

[beaufortfrancois]

This is now fixed.