Move `rustdoc-types` crate to T-Rustdoc ownership.

[aDotInTheVoid]

Rendered

CC @rust-lang/rustdoc @rust-lang/infra

[pietroalbini]

From an infra point of view, I think we can just remove the GitHub section, and have someone from T-rustdoc ping infra on Zulip when the move needs to happen. Infra will then handle it like all repository moves we do.

[aDotInTheVoid]

This was discussed today in the T-rustdoc meeting

TLDR:

• Infra blocker now solved
• Needs editing to be clearer around gaurentees (both mainenence and API-wize)
• Can move to FCP after that.

[aDotInTheVoid]

I've written about the versioning and release guarantees we intend to provide. My impression from the meetings is that everyone broadly supports doing this.

@rfcbot fcp merge

[rfcbot]

Team member @aDotInTheVoid has proposed to merge this. The next step is review by the rest of the tagged team members:

• [x] @GuillaumeGomez
• [x] @Manishearth
• [ ] @Nemo157
• [x] @aDotInTheVoid
• [ ] @camelid
• [x] @fmease
• [ ] @jsha
• [x] @notriddle

Concerns:

• ~~resolve versioning-strategy-clarity~~ resolved by https://github.com/rust-lang/rfcs/pull/3505#issuecomment--2083148599
• ~~versioning-strategy-clarity~~ resolved by https://github.com/rust-lang/rfcs/pull/3505#issuecomment--2083148790

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

[aDotInTheVoid]

I'd like to make sure that @Manishearth is happy with my resolution to https://github.com/rust-lang/rfcs/pull/3505#discussion_r1443544643 before merging.

@rfcbot concern versioning-strategy-clarity

[Manishearth]

Versioning strat lgtm!

[aDotInTheVoid]

@rfcbot resolve versioning-strategy-clarity

[fmease]

To make sure I understand the version strategy correctly, in practical terms does this mean we're going to abandon rustdoc_json_types's FORMAT_VERSION constant in favor of updating the package version (in Cargo.toml)? Essentially migrating from today's pub const FORMAT_VERSION: u32 = $N; to version = "0.$N" before we hit 1.0?

@rfcbot reviewed

[aDotInTheVoid]

does this mean we're going to abandon rustdoc_json_types's FORMAT_VERSION constant in favor of updating the package version

No, not at all. We're going to keep increasing FORMAT_VERSION whenever we change the format, and versioning the crates.io release according to SemVer. Those 2 versions are not necessarily linked, eg we could go from pub struct Id(pub String) to pub struct Id(String) without needing to bump FORMAT_VERSION, but it would be a breaking change for the cargo version.