You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by Julian Hyde <jh...@apache.org> on 2015/11/20 01:14:58 UTC
branch-release
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>
Re: branch-release
Posted by Jesus Camacho Rodriguez <jc...@hortonworks.com>.
Julian,
My bad, sorry about that. I thought branch-release should point to the HEAD of branch-1.5.
--
Jesús
On 11/20/15, 1:14 AM, "Julian Hyde" <jh...@apache.org> wrote:
>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>