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?
I assume the change will not be abrupt, and people will be notified of the change ahead of time, so we can adjust our scripts accordingly. There are some info about branch renaming here: https://github.com/github/renaming On Tue, Mar 9, 2021 at 4:31 PM 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/