tl;dr: I suggest that we avoid committing to master branch until the Avatica release is final.
Avatica is being released from branch-avatica-1.7, while Calcite development continues on master. After the release, we'll want to bring any Avatica changes back onto master branch, which will become Avatica's dev branch again. It would nice (not critical) if we could avoid a rebase and force push after the Avatica release, so I suggest that we avoid committing to master until the Avatica release is final (probably early next week). Julian
