[VOTE] Switch 'master' to 'main' branch for repositories
mail at david-bauer.net
Sun Mar 5 10:12:53 PST 2023
to keep it short - I have no oversight over how complicated this change is. From my understanding, we keep the
master branch around with the respective version and continue on main, to not break downstream. In that direction I'm fine,
but I have no idea about our infra / automation.
Given how many projects are transitioning, is any writeup available with the challenges (anticipated / unforseen) were
discovered? The would provide more confidence.
I don't want to hinder the decision however, so I remain to stay neutral.
In case we can not find a consensus (for now), maybe we can make smaller steps by using "main" for new projects and update
our components (netifs, ubus, ...) primary branch name. We'd have to do this anyhow, don't we? ;)
On 2/27/23 08:05, Felix Fietkau wrote:
> Hi all,
> More and more projects are switching their repositories to use the 'main' branch instead of the 'master' branch. This also includes many Linux upstream trees as well. Some trees are even removing their 'master' branches already.
> I think this is becoming more and more mainstream and expected of projects, so we should do the same.
> I would like to propose the following:
> 1. Change the git server side to automatically update the 'master' branch, whenever an update is pushed to 'main'.
> It's important to have a long transition period in order to avoid breaking downstream users' workflows.
> 2. Change the git server side to refuse a push to 'master' if 'main' exists. This avoid accidental branch divergence
> 3. Developers simply change their git configs to always push to 'main'
> Once this change is well established, we can look into removing 'master', but we should definitely take our time with that.
> - Felix
> openwrt-adm mailing list
> openwrt-adm at lists.openwrt.org
More information about the openwrt-adm