Hi Peff, On Fri, 13 Nov 2020, Johannes Schindelin wrote: > On Fri, 13 Nov 2020, Jeff King wrote: > > > I'm on the fence whether there should be a deprecation period or major > > version bump for the final patch, but making the tests flexible enough > > to handle the before and after state seems like it can be done uncoupled > > from the actual default-flip. > > [...] It's not like the median developer is creating new repositories on > a regular basis, and if they do, chances are that they go with whatever > branch name happens to be the initial one. > > What is much more common is that developers clone existing projects. And > guess what, many of those projects already use a different default branch > name. And developers seem to accept that and just go on with their lives. After sending off this mail, I felt a bit bad about not backing this up with data. Whatever telemetry I would be able to pull would not be representative, and I would not be at liberty to share it anyway. So I asked Alex Mullans of GitHub (who is in charge of the default branch name switch to `main` there) whether he has any data I could share publicly and he said: "Across GitHub, 1/4 of daily pushes (and growing) go to `main`." Seeing as the branch name to be used in newly-created repositories on GitHub changed only very recently (October 1st, i.e. some 6 weeks ago), I highly suspect that this number means that _a lot_ of existing projects have changed their primary branch name to `main`, and seem to be quite happy with it. All this is to say that I consider it unnecessary to have a long deprecation period or major version bump for this patch series, based on available public data. The name `main` is already in wide-spread use (and growing) as primary branch name of Git projects. Ciao, Dscho
