How does pmfow's versioning work?

pmfow uses a slightly modified version of the Semantic versioning method, which, in short, means that each release follows the x.y.z format, in which x represents the Major version number, y represents the Minor version number and z represents the Patch number.

In pmfow's case, the x number is currently 0, which means that it is constantly changing notoriously in some aspects and there are a lot of features that are almost fundamental for any package manager that are not fully implemented in pmfow, if at all.

The y number changes every time there is a relatively big update with new features and the z number changes every time there are more minor changes, additions and bug fixes.

There are cases in which the version number is followed by a hyphen and a small string of text with a number (example, 0.3.0-beta or 0.2.0-rc1), which represents a development/unstable release. For pmfow in particular, the most common ones are -beta and -rcx (where rc means Release Candidate and x is a number).

There are also very specific cases in which there can be a w number, which changes the format to x.y.z.w (example, 0.1.4.1), but this only happens in specific cases and it only really adds a single change, whether it is a bugfix or something like that.