THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Table of Contents
Version policy
4-digit version string digit semantic versioning string is used: x.y.z.h
- "x" means major MAJOR version
- "y" means "minor" MINOR version
- "z" means maintenancemeans PATCH
- "h" means hotfix
- "x" and "y" number changes mean catalog change needed.
hot fixes
MAJOR version change also means catalog changes.
| Info | ||
|---|---|---|
| ||
We switched back to 4-digit version policy per discussion in July 2016: mail archive: http://mail-archives.apache.org/mod_mbox/incubator-hawq-dev/201607.mbox/%3CCAE44UQcymo%3D8rBhE8b5bQ3qV-wH8Bvi0WXC89bqJgj%2Bh7Rzw9g%40mail.gmail.com%3E |
- "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
...
Branching
- Keep almost all the major/minor release work on Master branch
- When we want to do a major/minor release, tag it on master create a release branch
- Branch only will also be needed when doing hotfix patch releases:
- Example: : for 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 Put the fix and tag to 2.0.x, if applicable on Master, put it on master too. Finally, tag 2.0.1 release on 2.0.0.x