Hi all, while setting up the new build job, I noticed that we are also one of the projects still using a master branch.
I know this is sometimes discussed controversially, but I think we should rename it. It doesn’t cost us much and I think if this makes some people here feel more welcome, I am happy to go with that. In plc4x we decided to follow this naming scheme, which I quite like: * Development is done on the “develop” branch, which is considered the default branch * Releases are merged to the “release” branch, which is a protected branch * When releasing a version 1.2.0 we create a release/1.2 branch and for the release do a release/1.2.0 tag … version 1.2.1 is a bugfix release and would be done and tagged in the release/1.2 branch too (The benefit of this is that there is no longer a question about “where is development done?” and “where are the releases?” cause the naming matches their purpose) I would propose we do it similar (even if having multiple things in one repo makes things a little more difficult … but I hope you get the general idea. What do you think? Chris
