See: https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx
While this is not something that needs to happen tomorrow, we'd like to start the discussions and see if this is possible in the near future. Glean recently has done this as well. Fenix is slightly more complicated because of our TaskCluster release setup/hooks (for Nightly etc) which Glean does not have yet. This will need more investigation and verification by rel-eng before the Fenix team can proceed with our (mostly small) tasks here.
The "master" reference on git can be traced back etymologically to a master/slave reference https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00066.html
We will also be making sure we stop using "blacklist/whitelist". Words matter.
The "master" reference on git can be traced back etymologically to a master/slave reference https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00066.html
TIL!
There is some work needed for Releng, but I don't think this has a high complexity. Here's what has to be done:
master
. This can be done by making this logic smarter.master
branch. We need to make this piece smarter too.main
instead. That said, that shouldn't be necessary once bug 1631839 is done. I sent an email out about a month ago and sent a reminder earlier today. If I don't hear any concerns, I'll handle it by the end of this month.Apart from that, I don't see anything else. One quick note: I only looked into Fenix, there may be some differences if we want to make the change on other mobile projects. @tomprince, do you see anything I might have missed?
Most helpful comment
The "master" reference on git can be traced back etymologically to a master/slave reference https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00066.html
We will also be making sure we stop using "blacklist/whitelist". Words matter.