THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Table of Contents
Version policy
34-digit semantic versioning string is used: x.y.z.h
- "x" means MAJOR version
- "y" means MINOR version
- "z" means PATCH
- "h" hot fixes
MAJOR version change also means catalog changes.
...
- Keep all 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 patch releases:
- Example: after 2.0, a hot fix on 2.0 is needed, cut a branch 2.0.x from 2.0. Put the fix to 2.0.x, if applicable on Master, put it on master too. Finally, tag 2.0.1 release on 2.0.x
...