THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- "z" and "h" changes do not contain catalog change.
Branching strategy
Goals for branching strategy
- Keep team focusing on one release at one time
- Ease CI and improve engineering efficiency
How to branch
- Keep almost all the work on Master branch
- When we want to do a release, tag it on master branch
- Branch only when doing hotfix releases: for example, after 2.0.0, a hotfix on 2.0.0 is needed, cut a branch 2.0.0.x from 2.0.0. Put the fix and tag 2.0.0.1 on 2.0.0.x