What I meant was that
https://github.com/apache/calcite-site/commit/81960613e7750a9191280719352ae941a7d6a22d#diff-efedb3376e58f7bcc03c666d03682ce3R154
looked like it was built from calcite's master branch, so the
documentation is missing.
The site branch does not have any commits for gradle:
https://github.com/apache/calcite/commits/site
If the changes need to be published immediately, then the commits should
also be cherry-picked into the site branch, which can then be built.
I agree that the site vs master branch is not easy to work with. I am
working with infra to get automated builds implemented, so that we won't
have to manually push the site as a first step towards making it easier.
Francis
On 8/01/2020 7:58 am, Vladimir Sitnikov wrote:
Can you cherry pick the appropriate commits for the migration
into the site branch?
What do you mean by that?
Can we just revert the invalid commits and be done with it?
I already suggested that the site update should be simplified,
and now we have clear evidence that the current process of "site vs master"
is prone to errors.
Vladimir
