[
https://issues.apache.org/jira/browse/CALCITE-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167271#comment-17167271
]
Michael Mior commented on CALCITE-4147:
---------------------------------------
Here's the plan forward as I see it:
# Replace all relevant references in documentation and build
scripts/configuration with "main"
# Audit CI for possible configuration changes external to the code base
# Announce the pending change to the mailing list and temporarily freeze
commits
# Ask INFRA to make main the default branch and disable pushes to master
# Ensure main is in sync with mater
# Unfreeze commits
I've pushed a first pass at these changes in a "main" branch on my fork. What
is not currently addressed is Avatica and the calcite-site git repository.
[~vlsi] since you did the heavy lifting with the recent Gradle changes, is
there anything about the build/release process that you think needs to be
changed? AFAICT, there isn't anything aside from documentation updates to
ensure releases will be made from the "main" branch, but I want to avoid any
unpleasant surprises.
> 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
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
