Versioning
Since version 0.225, the version string is compounded like the following: "x.xyy-z".
-
"x.x": gives the version of the protocol that is used by the AlertR instances to communicate with each other. This means that as long as the version part "x.x" is the same on all your AlertR instances, they are compatible to each other. Because AlertR is under active development, the used protocol can change in a new release (see the Protocol entry for further details about the used protocol). A change of this part in the version string can also affect the used configuration file of the AlertR instances.
-
"yy": gives the version of the used configuration file by a single AlertR instance. This part of the version string can be completely different by all AlertR instances and they are still compatible to each other (as long as the protocol is the same). This can happen when an instance gets more features without influencing all other AlertR instances.
-
"-z": gives the revision of the AlertR instance. This is an internal change (like a bug fix in the AlertR instance) that does not affect the protocol and the used configuration file.
To make the meaning of the version string clearer, here are some examples:
-
If your AlertR instance has the version 0.225-0 and the newest version in the repository is 0.225-1, you only have to execute the update script.
-
If your AlertR instance has the version 0.225-5 and the newest version in the repository is 0.226-0, you also have to update your used configuration file before you can start this AlertR instance again.
-
If your AlertR instance has the version 0.225-4 and the newest version in the repository is 0.300-0, the protocol has changed (and the used configuration file). This means in order to update this AlertR instance, you have to update all your AlertR instances to have a working system again (and also have to update the used configuration file).