-
Notifications
You must be signed in to change notification settings - Fork 0
Versioning
I'm using my own version of the semantic versioning system to version this project. The structure is pretty simple.
A major release is a release that brings a huge change to the software, and is usually considered something of a turning point, therefore NoteRibbon will most likely stay at 1.x.x_x and maybe 2.x.x_x.
A minor release is a release that brings a smaller change to the software.
A patch release is a release that brings bugfixes to an existing release.
In this project, the build number is the number that increments with every commit.
The structure of a pre-release is major.minor.patch-bN_build for a beta release and major.minor.patch-rcN_build for a release candidate, where rc stands for "release candidate" and N is the pre-release number. Some example pre-releases are 1.5.2-b3_47 and 1.5.2-rc4_73.
The structure of a stable release is major.minor.patch_build, which is actually just semantic versioning with an underscore instead of a dot for the build number. An example stable release: v1.5.2_74.