Kopano Core 8.7.20 Final
@joost Will this change be forwarded to 9.x, 10.x and/or 11.x? It seems, it has not been forwarded, yet.
BTW: What is the reason for having 9.x, 10.x and 11.x versions of Kopano core? “beta”, “even more beta” and alpha?
Sinux last edited by
The fix for https://jira.kopano.io/browse/KC-1973 is in all newer branches.
Fixes are backported as needed to release branches from master.
In this example, see https://stash.kopano.io/projects/KC/repos/kopanocore/commits/2ddd63cd55e236f382124ee2b6d7f41b12986848 for the actual backport commits.
All such commits have commit references to their commit wher the fix actually was developed in the commit message.
Understood. The memory exhaustion fix is picked from master branch into the release branches (kc-8.7.x, kc-10.x and kc-9.x). I can find them there.
However, the fix is only “released” or “tagged” to kopanocore-8.7.20 and kopanocore-11.0.2.
Dependant or downstream developers/packagers would likely want to use tags rather than branches to be more precise in what has been used.
Am I wrong? Or what is the reason for not “releasing” or “tagging” this fix?
Thanks for feedback
Yes, all backports become be part of a release/tag.