Skip to content
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

add component documentation url after the release #66

Open
stdweird opened this issue Nov 20, 2014 · 6 comments
Open

add component documentation url after the release #66

stdweird opened this issue Nov 20, 2014 · 6 comments
Assignees
Milestone

Comments

@stdweird
Copy link
Member

the 14.10 link on http://www.quattor.org/documentation/index.html is missing

@jrha
Copy link
Member

jrha commented Nov 20, 2014

So is the documentation.

@jrha jrha added this to the 14.10 milestone Nov 20, 2014
@ned21
Copy link
Contributor

ned21 commented Oct 26, 2017

@jrha Last release mentioned on http://www.quattor.org/documentation/index.html is 17.2. Does this need to be updated as part of the release?

@wdpypere
Copy link
Contributor

wdpypere commented Nov 1, 2018

@jrha we apparently tend to forget adding the versioned link. How about we remove the versions from https://www.quattor.org/documentation/index.html and just go with the reference to latest (http://quattor-documentation.readthedocs.io/en/latest)

@jrha
Copy link
Member

jrha commented Nov 2, 2018

Sounds good to me

@jouvin
Copy link
Contributor

jouvin commented Nov 2, 2018

I basically agree but the link shoud be to stable (last released version) rather than latest (master). I also agree that we could remove explicit links to specific version: there is a menu in RTD that allows to do it if you really need it and it reflects only the version that are really available, as we may purge old versions from time to time.

@wdpypere
Copy link
Contributor

wdpypere commented Nov 5, 2018

@jouvin I do agree, but as it stands now stable and lastest are really the same. We don't have a release policy/strategy for the documentation.

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

No branches or pull requests

5 participants