-
Notifications
You must be signed in to change notification settings - Fork 162
Docs point to master's (1.0.0a0) release intead of a stable release (0.12.3) #966
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can probably look at adding a version to the docs somewhere, but latest always means master, that's just how RTD works. |
We can also change the default, as it appears to default to latest, which is not what we want. |
@asvetlov Have you got access to this one on RTD? |
Or @argaen? |
yeah, I probably could have made that point more clear. This is all I'm suggesting to do here really. |
A coworker and I just had a bit of confusion with the aiocache code. We were referencing the latest docs, naively assuming that it was for 0.12.3, but nothing was matching up with the actual module code. We finally realized that the "latest" docs actually point to an alpha release, 1.0.0.a0, which appears to significant compabilities issues with earlier releases.

https://aiocache.aio-libs.org/en/latest/:
That was really confusing. We're also not able to select 0.12.3 as a version so we're just going with 0.12.2 for docs. Maybe "stable" is 0.12.3 but I can't tell as the version is missing from the page when I select "stable":
Not sure if this all was intentional but it sent us for a wild goose chase. If it was intentional, I'd re-think it. The default docs that load shouldn't be unreleased code.
The text was updated successfully, but these errors were encountered: