I would like to rename the default branch in arrow-datafusion next. I have a PR up with the required changes:
https://github.com/apache/arrow-datafusion/pull/5280 I will submit a request to INFRA in the next few days to rename the default branch if there are no objections, and I will merge this PR once that has happened. Thanks, Andy. On Mon, Jan 23, 2023 at 12:30 PM Andy Grove <andygrov...@gmail.com> wrote: > The default branch in https://github.com/apache/arrow-ballista is also > now "main". > > I will wait until we have gone through the release process in Ballista and > DataFusion Python before proposing that we make these same changes in > DataFusion. > > On Sun, Jan 22, 2023 at 8:10 AM Andy Grove <andygrov...@gmail.com> wrote: > >> The default branch in https://github.com/apache/arrow-datafusion-python >> is now main. >> >> The process was simple for this repo - file an issue with INFRA, create a >> PR to replace master with main where appropriate (docs and workflows). >> >> I plan on doing the same for Ballista and DataFusion over the next week >> or two. I am not very active in arrow-rs, so I will leave that one for >> someone else to pick up. >> >> On Thu, Jan 19, 2023 at 3:11 PM Jacob Wujciak >> <ja...@voltrondata.com.invalid> wrote: >> >>> Thanks for moving this forward! In apache/arrow we have an umbrella issue >>> [1] and I think we are at the point where we are ready to ask INFRA to >>> rename the default branch to main. >>> Thanks to Fiona and Kevin for their work on the hardcoded branch names in >>> the dev tooling that was blocking this! >>> >>> Unless there are any objections we can initiate the switch after the >>> release. >>> >>> [1]: https://github.com/apache/arrow/issues/31142 >>> >>> On Thu, Jan 19, 2023 at 8:49 PM MAURICIO ANDRES VARGAS SEPULVEDA >>> <mavarga...@uc.cl.invalid> wrote: >>> >>> > yes, please! >>> > >>> > >>> > ——— >>> > >>> > Mauricio Vargas Sepulveda >>> > >>> > Master's Representative >>> > >>> > UofT Political Science >>> > >>> > ________________________________ >>> > From: Andy Grove <andygrov...@gmail.com> >>> > Sent: January 19, 2023 2:44 PM >>> > To: dev@arrow.apache.org <dev@arrow.apache.org> >>> > Subject: Re: Proposal: renaming the 'master' branch to 'main' >>> > >>> > I have filed issues in the Arrow Rust repos (let me know if I missed >>> any) >>> > >>> > https://github.com/apache/arrow-rs/issues/3569 >>> > https://github.com/apache/arrow-datafusion/issues/4994 >>> > https://github.com/apache/arrow-ballista/issues/618 >>> > https://github.com/apache/arrow-datafusion-python/issues/144 >>> > >>> > >>> > >>> > On Tue, Jul 26, 2022 at 8:19 AM Andrew Lamb <al...@influxdata.com> >>> wrote: >>> > >>> > > I am in favor of making the switch in arrow-rs as well -- can someone >>> > file >>> > > an issue so to start that discussion? >>> > > >>> > > On Tue, Jul 26, 2022 at 9:43 AM Kevin Gurney <kgur...@mathworks.com> >>> > > wrote: >>> > > >>> > > > Hi All, >>> > > > >>> > > > Thank you for bringing up this topic again. >>> > > > >>> > > > @Neal - I am already the assignee for ARROW-15693, which involves >>> > > updating >>> > > > crossbow. I will work on completing this as soon as possible. >>> > > > >>> > > > Best Regards, >>> > > > >>> > > > Kevin Gurney >>> > > > >>> > > > ________________________________ >>> > > > From: Remzi Yang <1371656737...@gmail.com> >>> > > > Sent: Monday, July 25, 2022 11:32 PM >>> > > > To: dev@arrow.apache.org <dev@arrow.apache.org> >>> > > > Subject: Re: Proposal: renaming the 'master' branch to 'main' >>> > > > >>> > > > Should we also do this change in arrow-rs? >>> > > > >>> > > > Remzi >>> > > > >>> > > > On Tue, 26 Jul 2022 at 11:25, Neal Richardson < >>> > > neal.p.richard...@gmail.com >>> > > > > >>> > > > wrote: >>> > > > >>> > > > > Many of the subtasks on >>> > > > https://issues.apache.org/jira/browse/ARROW-15689< >>> > > > 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< >>> > > > 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>><< >>> > > > > > 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 >>> >><< >>> > > > > > >>> 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 >>> > > > > >>> > > > > > ><< >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>> 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>><< >>> > > > > > 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>><< >>> > > > > > 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 >>> > > > > >>> > > > > > ><< >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>> 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>><< >>> > > > > > 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><< >>> > > > http://pacha.dev/blog<http://pacha.dev/blog>>> >>> > > > > > >> > >> >>> > > > > > >> > > >>> > > > > > >> > >>> > > > > > >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>> >>
