I think this is a great idea. Users of older versions can refer to the
appropriate version of the docs.
If we do want to go down this path, we need to look at the content in
https://calcite.apache.org/docs/ and decide what should be versioned and
what should just be on master. There are also links to Avatica docs in
the side bar and it would be a bit strange to have them always point to
the master version of Avatica.
On 9/12/2019 7:53 am, Vladimir Sitnikov wrote:
There are changes
such as documentation for new features, etc that should not be published
immediately
Could we publish "master" documentation under /master or /nightly folders?
Anyway, it makes sense to publish multiple versions of the documentation.
So why don't we publish master documentation as well?
For instance:
https://docs.gradle.org/nightly/userguide/userguide.html
https://docs.gradle.org/6.0.1/userguide/userguide.html
https://docs.gradle.org/5.6.4/userguide/userguide.html
And so on.
I suggest we drop "site" branch, and build the site from "master + release
branches (or tags) for the past releases".
Then the site update would be as follows:
- commit to master
- done
Vladimir
