Currently the WIP documentation for the newest Version can be found at “master” i.e.
The latest stable versions documentation can be found at “10.4” i.e.
And the old stable version at “9.5” i.e.
The documentation for the eLTS versions can be found at links like “7.6” i.e.
We provide no documentation for past minor versions. So one 10.4 got released we maintain not documentation for 10.3.
This leads to the master version (even if its still mostly WIP and only in interest for rare cases) and versions often linked to be most prominent on Google. Often all you can find is documentation for versions 7.6 and master = 11. Once we start working on the documentation for a new version the current stable version gets renamed.
Always use the main version
v11 would be the current WIP version
v10 the current stable
v9 the old stable
v8 the elts
downside links to v10 always point to v10 and do not promote v11 once it is stable
Use descriptive links
develop is version 11
stable is version 10
older versions are v9, v8 and so on
downside on new releases links pointing previously at 10 now point at 11
The best of both worlds?
using both notions with redirects, symlinks and or canonical urls?
keep everything as it was
Additionally I would suggest to have a link at the top of each document to the current stable version when you are using another version.