Clean up number of versions on readthedocs

[dstansby]

There's a lot of doc versions available on readthedocs, and it would be nice to slim these down. I think a good start would be to just keep the last version of every 2.x release (e.g., drop 2.3.0, 2.3.1, and keep 2.3.2). I'm not sure who has permissions on readthedocs, but I would be happy to do this if someone can give me the right permissions.

[TomAugspurger]

If possible, it'd be nicer to just hide these from the version UI to avoid breaking links pointing to those URLs.

[dstansby]

Looks like that's possible by changing the versions to hidden, which hides them from the version switcher and search engines, but keeps the links alive.

[jhamman]

I've added everyone on @zarr-developers/python-core-devs (that had an account) as maintainers on read the docs (including @dstansby )

[dstansby]

Thanks! I've:

• Hidden micro versions as suggested in the top comment
• Removed the 2.5.0 build, because there's a v2.5.0 build too which I assume is the real docs
• Removed the latest build, because it was duplicating main (and I think main is a clearer indication that it's a development branch IMO, but happy to switch the other way)
• Added a support/v2 build so we can see what the dev version of the v2 docs looks like

[jhamman]

Removed the latest build, because it was duplicating main (and I think main is a clearer indication that it's a development branch IMO, but happy to switch the other way)

I reverted this change as I know of a few downstream projects that link to latest via intersphinx.

xref: pydata/xarray#9652 (comment)

[dstansby]

Woops, thanks for fixing that!