Problem that’s happens fairly often.
Bugfixes applied to the master and also affecting other versions are not applied to the other versions.
Example
15761 FIX epower: Check levels if power is 0 · Checkmk/checkmk@9734a6f · GitHub
This problem is also existing in 2.2 at the moment but was already fixed some months before in the master.
It is not helpful the write will be included in 2.3.0b1 if there is 2.2 the “stable” version at the moment.
2 Likes
As it was a pull request, we at the moment only merge them in master. For bug fixes reported via our support channels, we also backport them to stable versions as per our support policies.
Backporting pull requests in general will be a tough thing, because it will reduce our ability to merge pull requests due to the potentially much higher effort. Especially since distinguishing a new feature vs. a bug is not trivial.
Then it would be better to merge pull requests for bug fixes only against the actual stable/available version. The current situation causes much much work.
You see a bug in the latest stable and need to search for a solution only to see at the end that the bug is only fixed inside the master branch what no one wants to use 
- the master branch version i mean.
The biggest problem here is, that the master branch has already such big difference to the actual 2.2, that it is nearly impossible to find the same code pieces.
But then you also see the problem. Right now, it will also involve a lot of effort then our side to backport them.
What will help in that regard would be us finishing the current refactoring (incl. moving of files) efforts in checks & agents which are port of the developer APIs for rulesets, metrics, active checks and special agents.