pSysmon version numbering

The version number is a standard triplet of integers: MAJOR.MINOR.MICRO. Depending on what kind of changes are applied to the source code, the major, minor or patch number is incremented. The rules for the version number increments are (taken from Producing Open Source Software, Fogel 2010):

micro
Changes to the micro number only (that is, changes within the same minor line) must be both forward- and backward-compatible. That is, the changes should be bug fixes only, or very small enhancements to existing features. New features should not be introduced in a micro release.

minor
Changes to the minor number (that is, within the same major line) must be backward-compatible, but not necessarily forward-compatible. It's normal to introduce new features in a minor release, but usually not too many new features at once.

major
Changes to the major number mark compatibility boundaries. A new major release can be forward- and backward-incompatible. A major release is expected to have new features, and may even have entire new feature sets.

Backward compatibility means, that new versions have to be able to deal with the data produced by the older versions (e.g. the project file or the database structure) within the same version line.
Forward compatibility means, that new versions are not allowed to produce any data (e.g. project files or the database structure) that can't be read by any older version within the same version line.

The rules defined above do not apply to releases of the version line 0.0.x. This version line is reserved for the initial development release and it will contain major changes on micro number changes.