Munin releases are identified by version numbers, based on the following structure:
[major versjon] . [minor version] . [release number]
E.g. in the Munin release 1.2.6, the major version is 1, the minor version is 2, and the release number is 6.
- If the minor number is odd, it indicates a development branch. In a development branch, features and plugins may be added (and removed!).
- If the minor number is even, the branch is considered stable. Within the same minor version, bugs are fixed but no new features are added.
When a development branch is considered suitable for production use, it will be "promoted" to a stable release by increasing the minor version number. For instance, when the 1.3 branch is sufficiently stable it will change to 1.4.0 and enter a state of feature freeze where only bugs and other kinds of functionality issues will be fixed.
At the same time, 1.3 will fork into a new development branch as 1.5.0 - becoming the branch into which new improvements, new features and new plugins will be introduced.