I am definitely for unifying the branches, it is quite annoying to remember what branch is the main branch in every repository. I don’t quite care what is that branch as long as we get to one name. develop sounds cool, but it’s extra step when you create new plugin, so it got us to master on most plugins (plugin maintainers just went with git default )
While I originally thought develop would be the best, after reading @ezr-ondrej’s comment I voted for main, which is not the git default. That’s quite pragmatic, new plugins will start with whatever the default is for the new repo.
I would counter that since all of the core repos use develop and these also have the biggest amount of automation around them, changing from develop to something else would require a lot of work. On the other hand, most plugin automation uses the same few tasks with just different variables for the specific plugin, so that changing all of them in one go would probably be easier.
If we modify the plugin template default branch to develop I think that people who use it as a template repo will also get the same branch name.
So in short - I’m for switching all to develop.
I agree with @tbrisker. Given the whole mess where Github has picked a default of main but git itself hasn’t, it’s still arbitrary. We must document explicit instructions to use something else than master anyway so we may as well standardize on develop to reduce the impact on automation.
Today nightly RPM builds use develop in the release to refer to the branch. Would we change that to main as well? It feels like a step back.
We also have x.y-stable branches. develop and stable are very clear and related. stable and main aren’t. I know at least the discovery plugin also has stable branches.
All in all, I think develop is just the better choice.