Le 14/02/2022 à 21:45, Neal Richardson a écrit :
There was discussion of this back in 2020 [1], and the consensus at the
time seemed to be to wait and see where git and GitHub would land before
making what could be a disruptive change. I support reopening the
discussion.
It looks like quite a few ASF projects have switched to 'main' by now [2],
and in order to do so, we'd need a vote/consensus thread here and then make
an INFRA issue (like [3]).
We also need someone to take responsibility for ensuring that all CI
jobs and other automation is updated for the change. Presumably that
could be the proponent.
Regards
Antoine.
Neal
[1]: https://lists.apache.org/thread/hyc6nxn6k2c19g9h4wj4khoysvwomj41
[2]:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20INFRA%20AND%20status%20%3D%20Closed%20AND%20text%20~%20%22main%20branch%22%20ORDER%20BY%20created%20DESC
[3]: https://issues.apache.org/jira/browse/INFRA-21723
On Mon, Feb 14, 2022 at 3:25 PM Mauricio Vargas <mavarga...@uc.cl.invalid>
wrote:
+1
On Mon, Feb 14, 2022 at 3:24 PM Fiona La <fion...@mathworks.com> wrote:
Hello all,
In order to be more inclusive and align with the Git<
https://sfconservancy.org/news/2020/jun/23/gitbranchname/> and GitHub<
https://github.com/github/renaming#new-repositories-use-main-as-the-default-branch-name
standards for the default branch of new repositories, I would like to
propose renaming the ‘master’ branch to ‘main’ in the Arrow project. I am
not sure if there has already been discussion about this, but I tried
searching the mailing list archives and did not see anyone mention this
yet.
In terms of tooling, GitHub has enabled renaming branches from the web
UI<
https://github.com/github/renaming>. I’m happy to help with this change
in any way that I can!
Thank you,
Fiona
--
—
*Mauricio 'Pachá' Vargas Sepúlveda*
Site: pacha.dev
Blog: pacha.dev/blog
