[
https://issues.apache.org/jira/browse/CALCITE-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524546#comment-17524546
]
Julian Hyde edited comment on CALCITE-4147 at 4/19/22 7:12 PM:
---------------------------------------------------------------
The only dependency I know between Calcite and Avatica is that Avatica's CI
pulls Calcite's master branch. The 'git clone' command doesn't refer to
Calcite's master branch by name, but the CI task refers to itself as Avatica's
master branch in a few places. See
[main.yml|https://github.com/apache/calcite-avatica/blob/f48dbc8c10d761d52a289d37eaf8e52b90239fa6/.github/workflows/main.yml#L47].
I think it's safe to rename Calcite and Avatica independently.
was (Author: julianhyde):
The only dependency I know between Calcite and Avatica is that Avatica's CI
pulls Calcite's master branch. The 'git clone' command doesn't refer to
Calcite's master branch by name, but the CI task refers to itself as Avatica's
master branch in a few places. See
[main.yml|https://github.com/apache/calcite-avatica/blob/f48dbc8c10d761d52a289d37eaf8e52b90239fa6/.github/workflows/main.yml#L47].
> 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: 1h 10m
> 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]
> * Default branch on GitHub (open INFRA ticket)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)