[
https://issues.apache.org/jira/browse/CALCITE-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167347#comment-17167347
]
Michael Mior edited comment on CALCITE-4147 at 7/29/20, 4:44 PM:
-----------------------------------------------------------------
{quote}It is very important to retarget before master removal.
{quote}
Good to know. On further investigation, it seems like Apache Mahout ended up
with an unexpected mass closing of PRs which we definitely want to avoid.
Although we could just keep master around for a time with pushes disabled. The
downside being that it wouldn't be possible to just press the merge button in
the GitHub web interface but those using the CLI won't experience any extra
friction.
There may also be some minor confusion based on the fact that the master branch
would still exist but I'm not sure that's going to be any more confusing than
having master deleted if people don't pay attention to the announcement of the
change.
was (Author: michaelmior):
{quote}It is very important to retarget before master removal.
{quote}
Good to know. On further investigation, it seems like Apache Mahout ended up
with an unexpected mass closing of PRs which we definitely want to avoid.
Although we could just keep master around for a time with pushes disabled. The
downside being that it wouldn't be possible to just press the merge button in
the GitHub web interface but those using the CLI won't experience any extra
friction.
> 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
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
