[
https://issues.apache.org/jira/browse/CALCITE-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526049#comment-17526049
]
Julian Hyde commented on CALCITE-4147:
--------------------------------------
Yes, I'd remove the references to {{{}new-master{}}}.
I agree that we should handle calcite and calcite-avatica in one INFRA ticket.
[~mmior], You are the author of PRs 2090 (calcite) and 124 (calcite-avatica).
The easiest thing would be if you file the INFRA ticket when those PRs are
rebased and ready to apply, and then you apply them after INFRA has renamed the
branches. Would you be OK doing that?
> 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)
