We have a special branch in git that always points to the most recent release. The branch is called “branch-release” [1].
In the last release we set it to the wrong commit id. It is an easy mistake to make, because the maven release plugin makes two commits in rapid succession. We want the earlier one, where the version number in pom.xml is “1.5.0”, not the later one, where it is “1.6.0-SNAPSHOT”. I have logged an INFRA ticket[2] to fix it. Future release managers please take note. Julian [1] https://github.com/apache/calcite/tree/branch-release <https://github.com/apache/calcite/tree/branch-release> [2] https://issues.apache.org/jira/browse/INFRA-10806 <https://issues.apache.org/jira/browse/INFRA-10806>
