RIBOT's versioning explained

[VLS]

We use the following semantic versioning:

branch.modules.revision


Branch:

The first digit indicates the major branch, for instance "v1.x", making a cohesive conglomerate of modules using the same interface.

Modules from the same branch are expected to be forward-compatible with newer RIBOT releases.

This means that if you place a module from RIBOT v1.10 on RIBOT v1.25, it is expected to work (from the previous version to the more recent version).

Modules:

This number indicates the total number of modules in a RIBOT release.

For example, RIBOT v1.15 has a net module count of 15, accounting for all module types (BetSelection, MoneyManagement, Display, Apps, etc.).

Revision:

A revision number raise happens when there is a change in the code but there are still the same number of modules in the new release.

In order to differentiate an updated version from the previous one, the revision number is increased.

For instance, when there is a bug fix on, say, v1.20, the fixed version comes online as v1.20.1; if there is another change but still the same number of modules, it launches as v1.20.2; and so on.

The revision number can be discarded when it's zero, since it is simply indicative of the first release.