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
+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
cont
+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 wrote:
> +1
>
> Thanks for resurfacing this Julian. Since main is becoming the default
> pretty much
+1 on moving this forward. Thanks for bringing it up again.
On Wed, Apr 13, 2022 at 3:52 AM Stamatis Zampetakis
wrote:
> +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
+1 as well given that the Github tooling for doing this has matured.
On 14/04/2022 2:20 am, Jacques Nadeau wrote:
+1 on moving this forward. Thanks for bringing it up again.
On Wed, Apr 13, 2022 at 3:52 AM Stamatis Zampetakis
wrote:
+1
Indeed the process seems to be rather easy with GitHub.
There seems to be consensus to move forward. (I do not presume that
all of the dissenters from last year's discussion have changed their
minds and are now on board. Their objections are on record in that
thread.)
I am moving discussion to the case,
https://issues.apache.org/jira/browse/CALCITE-414
