Skip to content

Versioning

Jump to bottom
Unseeable8710 edited this page Mar 25, 2025 · 4 revisions

Versioning system

I'm using my own version of the semantic versioning system to version this project. The structure is pretty simple.

Pre-releases

You might be wondering why I decided to use an underscore for the build number. Well, the answer is consistency. This is because the structure of a pre-release is major.minor.patch-bN_build for a beta release1 and major.minor.patch-rcN_build for a release candidate2, where rc stands for "release candidate" and N is the pre-release number.

Stable releases

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. 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. An example stable release: v1.5.2_74.

Clone this wiki locally