I, too, had to deal with this and ended up next. My branching strategy is to free myself from the release / version branch. As soon as the new version is cut, I will combine it to create and create the next release branch based on this. The master branch always contains the last / docs content, which seems to be javadocs. Then I advise the reader that if he wants to see the old version of javadoc for cloning the repository locally, check the branch of interest and load docs / index.html into the browser.
source share