Request: Provide an official way to *deprecate* a crate. NOT yank. Yank is stupid

I think that this should be a separate state ("maintenance not required") that is distinct from both maintained and unmaintained. I agree that a large number of crates, specially if they have little or no dependencies, are evergreen and require no maintenance. I think one trouble is that even crates that don't normally require maintenance may require it exceptionally (for example, a compiler bug was fixed but this crate was relying on it - if the crate owner is unresponsive, this should downgrade the crate from "maintenance not required" to "unmaintained") Anyway all such schemes for signaling maintenance should probably be opt-in. If the author does nothing, it should work as today.