On Tue, 2021-03-09 at 16:46 -0800, Mariatta wrote:
> > > 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/renamingHi Mariatta, Have you considered not deleting the master branch and instead simply adding a github workflow job that syncs main to master on pushes to main? The master->main Github redirection is great but perhaps not the best option for the CPython repo. I find it very useful for smaller projects, but for something as big as CPython I feel it will still cause too much breakage, and a not that trivial to notice one, too many people with too many workflows dependent on the branch name. Though, it can be argued the people that work on CPython and have such workflows will likely be in the loop regarding such change and so it isn't a big deal. Anyway, this was just something to consider, hopefully it was somewhat helpful :) Cheers, Filipe Laíns
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@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/I5PI2XOCBBLEAPFYBWTVNK25GKP3NITV/ Code of Conduct: http://python.org/psf/codeofconduct/
