Skip to content

Check use of latest for latest unreleased versions vs latest stable versions #6096

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

Closed
stsewd opened this issue Aug 22, 2019 · 7 comments · Fixed by #10877
Closed

Check use of latest for latest unreleased versions vs latest stable versions #6096

stsewd opened this issue Aug 22, 2019 · 7 comments · Fixed by #10877
Assignees
Labels
Accepted Accepted issue on our roadmap Good First Issue Good for new contributors Needed: documentation Documentation is required

Comments

@stsewd
Copy link
Member

stsewd commented Aug 22, 2019

We should check this in our docs and help texts, it's confusing for some users.

@stsewd stsewd added Needed: documentation Documentation is required Good First Issue Good for new contributors labels Aug 22, 2019
@stsewd
Copy link
Member Author

stsewd commented Aug 22, 2019

Here is a place where it needs clarification https://docs.readthedocs.io/en/stable/versions.html#version-warning and on the advanced settings Show version warning.

It should mention that the banner links to the latest stable version.

@stale
Copy link

stale bot commented Oct 6, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Oct 6, 2019
@stsewd stsewd added Accepted Accepted issue on our roadmap and removed Status: stale Issue will be considered inactive soon labels Oct 7, 2019
@KartikKapil
Copy link
Contributor

@stsewd is this issue still open ?

@stsewd
Copy link
Member Author

stsewd commented Jan 7, 2020

@KartikKapil yeah, but there is a PR in progress here #6143

@Blackcipher101
Copy link
Contributor

@stsewd Can I work on this issue

@stsewd
Copy link
Member Author

stsewd commented Jan 22, 2020

@Blackcipher101 if so, please use #6143

@humitos
Copy link
Member

humitos commented Sep 5, 2023

Related issue at #10674

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment