The master branch being the master branch

[stappersg]

Commits like

• 529d511 Merge branch 'master' into 0.10
• 18584a9 Merge branch 'master' into 0.9
• 0e1a9e6 Merge branch 'master' into 0.8
  indicate merging into the wrong direction.

N commits ahead of master is something for a feature branch, not for something that will be become a version.

What are the opinions of letting the master branch be the master branch?

[hecrj]

No such thing as merging in the wrong direction.

This is not a discussion worth having.

[stappersg]

Suggestion for creating future release branches, be in master branch and do git branch -c 0.11.

Later on, when a next release is due, git branch -c 0.12.

[hecrj]

Our release branches are different from master on purpose. There are certain changes in master that simply can't be released yet.

Suggestion for future comments: don't assume you know more about a project than the people involved with it. Don't assume they don't know basic stuff either.

Thanks for teaching me how to create a Git branch. I honestly don't know how I made it this far without such knowledge.