While we're at it, we should consider what version to link to:
Link to the exact version of rustls we currently depend on. For consistency, this requires updating all doc links each time we bump the version of rustls, which we haven't done consistently so far.
Link to /latest/. This stays up-to-date but will result in 404s if a future semver-incompatible version of rustls removes something we link to.
Link to /~0.21/. This is a special docs.rs redirection that will always link to the latest version in the 0.21 series.
So far I like (2) best. The issue of future breakage is a fairly small one, and linking to /latest/ is nice and simple.
Our documentation links out to rustls documentation for many things. For instance,
rustls_client_config_builder
links to https://docs.rs/rustls/0.20.0/rustls/struct.ConfigBuilder.html. We should update these links for the 0.21 release.While we're at it, we should consider what version to link to:
/latest/
. This stays up-to-date but will result in 404s if a future semver-incompatible version of rustls removes something we link to./~0.21/
. This is a special docs.rs redirection that will always link to the latest version in the0.21
series.So far I like (2) best. The issue of future breakage is a fairly small one, and linking to
/latest/
is nice and simple.