-
Notifications
You must be signed in to change notification settings - Fork 1
Version Naming Convention
ben-lin edited this page Jul 24, 2012
·
5 revisions
Start with lowercase v, the version number contains 3 digits separated by 2 dots. The first number from the left determines if it is a major release. For example the whole architecture changes, performance improvement, API renamed or works differently. The second number determines if there are new APIs added. The last number determines if there are bug fixes.
- first digit: major release, architecture changes, performance improvement, API renamed.
- middle digit: new APIs added
- last digit: refactoring, bug fix
- Alpha or beta releases always uses even numbers for the first digit. ex. v0.1.3, v4.2.7
- Stable releases always uses odd numbers for the first digit. ex. v1.0.12, v3.5.1
- One version can have multiple bug fixes.
- We can have new APIs added with bug fixes in one version, just go up with the middle digit. ex. v2.3.2 -> v2.4.0
- When update dependency packages, the rules are the same as above.
- Always use stable releases on production.
- It is safe to upgrade with the middle digit or the last digit changed version without changing app code.