4. Feature branches
4
May branch off from: develop
Must merge back into: develop
Naming convention: anything except master,
develop, release-* or hotfix-*
Should delete after finishing feature development
5. Release branches
5
May branch off from: develop
Must merge back into: develop and master
Naming convention: release-*
Must be tagged into master after merging
Example: change master version from 0.2 0.3
Should delete after finishing feature development
6. Hotfix branches
6
May branch off from: master
Must merge back into: develop and master
Naming convention: hotfix-*
Must be tagged into master after merging
Example: change master version from 0.2.1 0.2.2
Should delete after finishing feature development
8. Apply branch model into Rubichat
8
Outline rubichat versions:
Version: 0.6: rubichat works well in giaybac.com
Version: 0.8: rubichat admin, branch off from 0.6
Version: 0.9: rubichat system, branch off from 0.8
Version: 1.0: merge 0.6 and 0.9
Rubiweb will be developed in branch
“origin/develop”
Feature upgrade will be developed in a feature
branch. Example: move data from Redis to
MongoDb