[
https://issues.apache.org/jira/browse/CALCITE-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525597#comment-17525597
]
Francis Chuang commented on CALCITE-4147:
-----------------------------------------
Grepping through Avatica's and Calcite's repo, I noticed there's a travis job
that triggers a build on changes to a branch called new-master:
https://github.com/apache/calcite-avatica/blob/master/.travis.yml#L65
https://github.com/apache/calcite/blob/master/.travis.yml#L56
I was not able to find the branches on Github, may be it's safe to remove that
branch's in .travis.yml as part of this change.
> Rename "master" branch to "main"
> --------------------------------
>
> Key: CALCITE-4147
> URL: https://issues.apache.org/jira/browse/CALCITE-4147
> Project: Calcite
> Issue Type: Improvement
> Reporter: Michael Mior
> Assignee: Michael Mior
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Settings to change:
> * GIT_COMMIT in [Calcite-Snapshots Jenkins
> pipeline|https://builds.apache.org/view/A-D/view/Calcite/job/Calcite-Snapshots/configure]
> * Rename [Calcite-Master Jenkins
> pipeline|https://builds.apache.org/view/A-D/view/Calcite/job/Calcite-Master/configure]
> * Ask infra to rename the branch on GitHub using Github's renaming tool
> (open INFRA ticket)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
