You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »


Version policy


4-digit version string is used: x.y.z.h

     - "x" means major version
     - "y" means minor version
     - "z" means maintenance
     - "h" means hotfix
     - "x" and "y" number changes mean catalog change needed. 
     - "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 all major/minor/maintenance release 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

 

 

 

 


  • No labels