As with any of these changes, the one and only inescapable side-effect is that users' local environments will not be able to be updated. GitHub has otherwise made it very simple to rename branches to accommodate this use case. https://github.com/github/renaming Any old references to master will on the GitHub site itself will reroute to main.
It's a small annoyance to make the Iceberg community more inclusive. For those that aren't aware of the why: https://en.wikipedia.org/wiki/Master/slave_(technology)#Terminology_concerns . On Mon, Oct 2, 2023 at 4:34 PM Hussein Awala <huss...@awala.fr> wrote: > +1 > > On Mon, Oct 2, 2023 at 11:27 PM Anton Okolnychyi <aokolnyc...@apache.org> > wrote: > >> +1 >> >> On 2023/10/02 20:12:37 Bryan Keller wrote: >> > Hearty +1 from me >> > >> > >> > >> > > On Sep 29, 2023, at 5:37 AM, Brian Olsen <bitsondata...@gmail.com> >> wrote: >> > > >> > > >> > >> > > >> > > >> > > +10000000 >> > > >> > > >> > > >> > > >> > > Let me know how I can help! >> > > >> > > >> > > >> > > >> > > On Fri, Sep 29, 2023 at 7:35 AM Jean-Baptiste Onofré >> > > <[j...@nanthrax.net](mailto:j...@nanthrax.net)> wrote: >> > > >> > > >> > >> > >> Hi guys, >> > > >> > > The Apache CoC (<https://www.apache.org/foundation/policies/conduct>) >> >> > > especially contains section 5 about the wording we use. Several >> Apache >> > > projects renamed the master branch to the main branch (Apache >> Karaf, >> > > ActiveMQ, Airflow, ...). >> > > As we already use main for go, rust, and python repositories, I >> wonder >> > > (for consistency) if we should not rename master to main on the >> "main" >> > > repository. >> > > >> > > Apache INFRA can do this "smoothly" but we would have to do some >> changes: >> > > \- update build.gradle >> > > \- update README.md >> > > \- update to GH Actions (in .github/workflows/*) >> > > >> > > Thoughts ? >> > > >> > > Regards >> > > JB >> > > >> > >> > >> >
