For now, least important of the milestone 02 issues. A standard semantic versioning system consists of 3 numbers - for instance, 1.2.3. The first number represents API changes that render it incompatible with calls from a previous version, second number represents smaller backwards-compatible API changes, and the third number represents minor bug fixes. 1.0.0 is the initial release build.
For the purpose of our application, there's an argument that 1.0.0 should be reserved for the final "release" build that represents our exam product. However, the distinction is, in my mind, largely semantic (as the name implies!). Keeping the major version number at 0 for the entirity of our development span somewhat defeats the purpose of it. I want to adapt the system to a versioning that makes sense for us in particular.
For now, least important of the milestone 02 issues. A standard semantic versioning system consists of 3 numbers - for instance, 1.2.3. The first number represents API changes that render it incompatible with calls from a previous version, second number represents smaller backwards-compatible API changes, and the third number represents minor bug fixes. 1.0.0 is the initial release build.
For the purpose of our application, there's an argument that 1.0.0 should be reserved for the final "release" build that represents our exam product. However, the distinction is, in my mind, largely semantic (as the name implies!). Keeping the major version number at 0 for the entirity of our development span somewhat defeats the purpose of it. I want to adapt the system to a versioning that makes sense for us in particular.