I don’t think we have resources to maintain one doc per branches and that’s why we changed the website last year with 'Stable version (3.4/3.6/3.8/3.10)". Making (and using) only one link for all would make sense so that the URL is not misleading users https://geonetwork-opensource.org/manuals/trunk/en/index.html (maybe a redirect could be set up in the website ?)
and maybe better identify which features is available in which version in the doc.
To be checked with Jose or Juan for the server setup, but I think all folders are pointing to the same folder.
Maybe we can simplify this to be https://geonetwork-opensource.org/manuals/en/index.html ?
and setup a permanent redirect for all other URLs?
I don’t think we have resources to maintain one doc per branches and that’s why we changed the website last year with 'Stable version (3.4/3.6/3.8/3.10)". Making (and using) only one link for all would make sense so that the URL is not misleading users https://geonetwork-opensource.org/manuals/trunk/en/index.html (maybe a redirect could be set up in the website ?)
and maybe better identify which features is available in which version in the doc.
I am uncomfortable using master to document a range of functionality across different versions as that is very hard to maintain. Reading Paul’s email … freezing documentation at each release is far cheaper to maintain. To make that work we would need to go back to the 3.8.x branch and change the submodule revision to just before the 3.10.x release notes were added.