Common Software Version Naming Conventions

Many developers wonder how to name version numbers when writing code or designing products. The most common simple form is V1.0.0 , while more complex formats may include dates and suffixes.

A general version naming convention can be expressed as major.minor.patch.date_stage , for example V1.2.3.20201228_rc .

Explanation of each part:

Major version (first number): Indicates large functional changes or architectural redesigns; updated at the project’s discretion.

Minor version (second number): Reflects moderate feature additions or enhancements, such as new permission controls or custom views.

Patch version (third number): Used for bug fixes or small tweaks; released whenever a serious bug is resolved.

Date version (e.g., 20201228): Records the date of the change; updated by developers whenever the project is modified.

Stage suffix (e.g., rc): Marks the development phase of the software (Alpha, Beta, RC, Release, etc.).

Software version stages:

Base: A placeholder version with basic layout but incomplete functionality.

Alpha: Early internal testing with many bugs.

Beta: Improved version with major bugs fixed, focusing on UI.

RC (Release Candidate): Nearly final, stable version ready for release.

Release: Final product delivered to users, sometimes denoted by the symbol (R).

Other naming conventions exist for specific tools: Keil MDK uses V5.33 (major and minor only), while IAR EWARM uses V8.50.9.33462 (serial number instead of date). Most software primarily relies on major and minor numbers, with other components varying by product.

In summary, you should now have a clear understanding of how to name software versions appropriately.