+1 Indeed the process seems to be rather easy with GitHub. I assume the changes will be propagated automatically to the Gitbox repo as well.
Stamatis On Tue, Apr 12, 2022, 10:41 PM Michael Mior <mm...@apache.org> wrote: > +1 > > Thanks for resurfacing this Julian. Since main is becoming the default > pretty much everywhere and the tooling has improved, I think several of the > criticisms of this are less relevant. Yes, it still does require work and > some things may break. But this is a one time change and only affects > contributors, not any consumers of Calcite artifacts. > > -- > Michael Mior > mm...@apache.org > > > Le mar. 12 avr. 2022 à 15:10, Julian Hyde <jh...@apache.org> a écrit : > > > In August 2020 Michael started a discussion[1] about renaming the > > 'master' branch in Git to 'main'. A majority of the community seemed > > to be in favor, although some people did not agree with the change. > > > > If I recall correctly, we did not move forward with the rename at that > > time in part because of tooling: GitHub tooling was not mature enough > > to guarantee that the change would be smooth. I now believe the > > tooling is mature. I have migrated several personal projects, and > > GitHub makes it very easy. > > > > I propose that we move forward with renaming the 'master' branch in > > the calcite, calcite-avatica and calcite-avatica-go repositories. I > > propose that we do calcite-avatica first, because it is less used than > > calcite. > > > > Julian > > > > [1] https://lists.apache.org/thread/7f2kpkf8lrq0mmt46lb2orsh39kq7dbs > > >
