Switch to Semantic Versioning #36
Description
What does this refer to?
The CI/CD pipeline currently targets working with build numbers rather than using actual version numbers. This is a poor practice to use.
What's wrong with it?
Build numbers are poor representatives of what actually changed within the code. Using semantic versioning is the standard in the software world and is much more useful for determining what changed, and which updates can be safely applied to a project without breaking it or requiring major reworking.
Switching to a semantic versioning pipeline might also make it easier to automate official releases instead of always pushing prereleases.
How can it be improved?
This can be improved by updating the build pipeline to reflect a semantic versioning standard instead of a build version.