[
https://issues.apache.org/jira/browse/CALCITE-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523877#comment-17523877
]
Julian Hyde commented on CALCITE-4147:
--------------------------------------
I started a [new discussion
thread|https://lists.apache.org/thread/0ktmy0kr14rg06w19zhhfqk3dljsgosx] and
this time no objections were voiced.
There were objections in last year's thread, and I do not presume that all of
those people have since been convinced. But a majority of the community seems
to be in favor, a minority seem to feel that's not worth the effort (for
reasons given in the 2021 thread), and I think we should now move forward.
I suggest we start with calcite-avatica-go (because it has fewer users and
lower activity than our other repositories). Steps as follows:
# File an INFRA ticket (similar to INFRA-22880);
# Commit changes to make the repo work with the new branch (including user
instructions and CI);
# Email instructions for users to upgrade their sandboxes.
When that process works, let's repeat for calcite and calcite-avatica.
[~mmior] or [~francischuang], Would you like to do this?
> 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.1#820001)
