THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Table of Contents
Version policy
3-digit version string digit semantic versioning string is used: x.y.z
- "x" means MAJOR version
- "y" means MINOR version
- "z" means PATCH - "h" means HOTFIX
MAJOR and MINOR version change also mean means catalog changes from HAWQ perspective.
Branching strategy
Goals
- Keep team focusing on one release at one time
- Ease CI and improve engineering efficiency
...
- Keep all major/minor release work on Master branch
- When we want to do a major/minor /PATCH release, tag it on master branch
- Branch only when doing patch releases:
- Example: after 2.0.0, a hotfix hot fix on 2.0.0 is needed, cut a branch 2.0.0.x from 2.0.0. Put the fix to 2.0.0.x, if applicable on Master, put it on master too. Finally, tag 2.0.0.1 release on 2.0.0.x