Semantic Versioning
Almost all versioning policies consists of four numbers. Typically each software version contains four components: major version number, minor version number, patch version number and build version number.
Major version number
- If you introduce a major change from the business perspective.
- If you are chaning intended use, or intended audience of the product.
- If you are introducing significant new risks to end-users.
- If you are introducing completely new version of software specification.
- If you are introducing significant new version of end user manual.
- If you are introducing backwards incompatible GUI changes.
- If you are introducing backwards incompatible API changes.
- If you need to notify existing users about changes in functionality.
- If you need to perform users tests with the specific changes.
- If you need to perform data migration procedure.
- If you need to perform upgrade process or procedure.
Minor version number
- If you are improvimg mitigation of existing risks.
- If you are improvimg details of existing specification(s).
- If you are improvimg details of existing user manual(s).
- If you are introducing backward compatible GUI changes.
- If you are introducing backward compatible API changes.
Patch version number
- If you are just fixing a number of bugs to existing specification.
Build version number
- If you are just making another build of same code-base.
- Author
Maciej Zagozda
Company founder, and director of engineering.
- Comments
- Leave a Comment