+1 for rekeased branch so this branch indicates that this is the current
release branch. For specific versions we have the rel/0.7

Am Mo., 15. Juni 2020 um 16:08 Uhr schrieb Christofer Dutz <
[email protected]>:

> Hi all,
>
> I would like to take the opportunity to discuss with you, if we should
> perhaps change the name of our “master” branch.
>
> I do know that currently the discussion is mainly based on the fact that
> for some people “master” seems to imply “slave” and this sort of maps to
> other cultural issues that might come up in conjunction with this. My
> suggestion actually doesn’t have anything to do with this reasoning, even
> if the thought was indeed sparked by this discussion. And if in the end it
> makes more people happy, that’s an even bigger benefit.
>
> The main reason is that I am working on a lot of project and every project
> sort of handles branch names differently. Some develop on “master” and
> release in release branches, some develop on “develop” and release to
> master etc.
>
> I really like developing on “develop” … the name of the branch sort of
> set’s what it’s used for … same with release and feature branches … however
> “master” sort of always droped out of this pattern.
>
> So I would like to suggest we rename “master” to “release(d)” … this way
> every new contributor will automatically know what’s used for what.
>
> What do you think?
>
> Chris
>

Reply via email to