We currently have “master” as current main version in the documentation. But what is “master”? Does it reflect the core “master” which is (currently) the unreleased 10.3-dev or does it reflect the latest release which is 10.2? If it refers to the unreleased master, we could update the docs as soon as a core patch is merged (and requires a change to the documenation). This is good from maintainance perspective. But possibly not from the users perspective because they get documentation for yet unreleased features.
I made a proposal to add an additional branch (latest) for latest release, keep working on master, updating documentation early, but use “latest” as URLs to link to. I think this would require a change on Intercept and is more work in the long run.
A less work-intensive alternative would be to affirm “master” (in docs) as being the equivalent to the core master which would mean it may contain not yet released changes.
Any thoughts? …