THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Table of Contents
Version policy
43-digit version string is used: x.y.z.h
- "x" means major MAJOR version
- "y" means minor MINOR version
- "z" means maintenance
- "h" means hotfix
- "x" and "y" number changes mean catalog change needed.
means PATCH
Increase:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes.
- Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
MAJOR and MINOR also mean catalog changes from HAWQ perspective.
- "z" and "h" changes do not contain catalog change.
Branching strategy
Goals
- Keep team focusing on one release at one time
- Ease CI and improve engineering efficiency
...
- Keep all major/minor/maintenance release work on Master branch
- When we want to do a major/minor/maintenance release, tag it on master branch
- Branch only when doing hotfix releases:
- 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 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