Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Version policy

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



titleVersion History

We switched back to 4-digit version policy per discussion in July 2016: mail archive:


Branching strategy


  • 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 release, create a release branch
  • Branch 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