I'm unsure about rust-semver as, even though it's deprecated, it's still on crates.io and has some usage. In the off chance that there's a need for a patch release, it would be annoying to have to unarchive the repo.

Also, I'm unsure about https://github.com/rust-lang/rustc-timing - are we sure that is unused?

I'm unsure about rust-semver as, even though it's deprecated, it's still on crates.io and has some usage. In the off chance that there's a need for a patch release, it would be annoying to have to unarchive the repo.

Hmm, I see your point, but in theory we could say this about almost anything that is archived? E.g. rustc-serialize was archived for some time, and probably no one expected that we will need to unarchive it, but then we still had to do a new release, so I think that this can basically happen with anything.

This crate seems to be superseded by much more popular alternatives, and I don't think that it would be very easy to do a new release anyway, since it hasn't been updated in years, and probably getting it to work on a recent compiler would be quite difficult. I think that it depends on save-analysis, which was already removed, AFAIK. Furthermore, its own README states that it is deprecated. So I would personally archive this.

Its maintainer also suggested archival here, although he wanted first to publish a release with a deprecation notice, which probably never happened (?).

Also, I'm unsure about https://github.com/rust-lang/rustc-timing - are we sure that is unused?

I haven't interacted with it in any way in the last ~2 years that I have been maintaining rustc-perf, and I don't recall seeing any code in the current codebase that would be interacting with it. @Mark-Simulacrum are you aware of any current usage of this repo?

Mark has confirmed that rustc-timing is no longer used, to his knowledge.