Many of the subtasks on https://issues.apache.org/jira/browse/ARROW-15689 have already been done. What's left is to update archery and crossbow, then we can ask Infra to make the switch. Is anyone able to take those subtasks on?
Neal On Mon, Jul 25, 2022 at 4:58 PM Matthew Topol <m...@voltrondata.com.invalid> wrote: > I'm in favor of it, for what it's worth. > > --Matt > > On Mon, Jul 25 2022 at 02:56:31 PM -0600, Wes McKinney > <wesmck...@gmail.com> wrote: > > hi all, > > > > Do you think we could make a push to make this happen after the 9.0.0 > > release goes out? > > > > Thanks > > Wes > > > > On Tue, Feb 15, 2022 at 2:32 PM Fiona La <fion...@mathworks.com > > <mailto:fion...@mathworks.com>> wrote: > >> > >> Thank you Antoine for bringing up the engineering work that is > >> required to enable this. And thank you Neal for sharing the link to > >> the previous discussion and creating the umbrella issue/breaking > >> down the tasks in Jira. > >> > >> I am happy to work on these subtasks to move the effort forward; > >> I’ll start with this subtask [1]. > >> > >> [1]: <https://issues.apache.org/jira/browse/ARROW-15692> > >> > >> > >> From: Neal Richardson <neal.p.richard...@gmail.com > >> <mailto:neal.p.richard...@gmail.com>> > >> Date: Tuesday, February 15, 2022 at 3:38 PM > >> To: dev <dev@arrow.apache.org <mailto:dev@arrow.apache.org>> > >> Subject: Re: Proposal: renaming the 'master' branch to 'main' > >> Good point Antoine, there is engineering work to be done to allow > >> this. > >> I've made an umbrella issue [1] and broke out a bunch of subtasks. > >> The idea > >> is to update our code (mostly CI stuff) to use the default branch, > >> whatever > >> it happens to be called, and then after that is done we will be > >> able to ask > >> INFRA to make the change. Those who are interested in seeing this > >> happen > >> can work on those subtasks, and we can check back once those are > >> done. > >> > >> Neal > >> > >> [1]: > >> <https://issues.apache.org/jira/browse/ARROW-15689><< > https://issues.apache.org/jira/browse/ARROW-15689>> > >> > >> On Mon, Feb 14, 2022 at 3:46 PM Antoine Pitrou <anto...@python.org > >> <mailto:anto...@python.org>> wrote: > >> > >> > > >> > 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><< > 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 > ><< > 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><< > https://issues.apache.org/jira/browse/INFRA-21723>> > >> > > > >> > > On Mon, Feb 14, 2022 at 3:25 PM Mauricio Vargas > >> <mavarga...@uc.cl.invalid <mailto:mavarga...@uc.cl.invalid> > >> > > > >> > > wrote: > >> > > > >> > >> +1 > >> > >> > >> > >> On Mon, Feb 14, 2022 at 3:24 PM Fiona La > >> <fion...@mathworks.com <mailto: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/><< > https://sfconservancy.org/news/2020/jun/23/gitbranchname>>> > >> and GitHub< > >> > >>> > >> > >> > >> > > >> < > https://github.com/github/renaming#new-repositories-use-main-as-the-default-branch-name > ><< > 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><< > 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<<http://pacha.dev/blog>> > >> > >> > >> > > > >> > > >
