The Steering Council unanimously believes this is the right thing to do. Fortunately GitHub makes it very easy from their side. We push a button and it makes the change for the repo and all PRs. Then when you visit the repo page in GH, it tells you exactly what commands to run to make the change in your local repo. It’s even cut-and-pasteable. We want to be mindful of the timing, both so that folks have plenty of notice to update their scripts and recipes, but also to coordinate with the release managers so that the switch happens when it won’t break the release process. Cheers, -Barry On Mar 9, 2021, at 16:27, Terry Reedy <tjreedy@udel.edu> wrote:
On 3/9/2021 3:27 PM, Pablo Galindo Salgado wrote:
The Steering Council just published the community update for February:
Thank you for posting this.
The Steering Council discussed renaming the master branch to main and the consensus was that we should do that.
I did not that this was an issue. This will break 4 of my .bat files (update repository and workspaces, build python.exes, run sphinx on docs, run coverage.) and, I presume, many other workflow scripts and bots. What is the upside? ('next (version)' might be more accurately descriptive, but 'main' works as the 'main branch we are working on'.) Does 'master' confuse people?
-- Terry Jan Reedy
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/EMXFMHSF... Code of Conduct: http://python.org/psf/codeofconduct/