Git branch names and workflow

For a long time at Multiple States we would include the version number in every branch name (eg master_1.2.3_kb_issue123). This has caused some issues as regularly on larger projects priorities change and things will go in to different branches. This causes confusion on pull requests.

I am looking at this new branching naming system:

master
master_kb_issue789 
staging
development
development_1.0.1
development_kb_issue456 
development_1.0.0
development_kb_issue123
development_kb_issue456

This allows for issue / fixes to merge to different branches if needed.

Read more

• GIT documentation
• Multiple States documentation