Kopano Core 8.7.20 Final

Joost

We have released Kopano Groupware Core 8.7.20 to the download server and our repositories.

This minor release fixes a memory exhaustion issue with the kopano-ical service, as mentioned in this blog post.

Please let us know if you run into any issues.

@joost Will this change be forwarded to 9.x, 10.x and/or 11.x? It seems, it has not been forwarded, yet.

https://stash.kopano.io/projects/KC/repos/kopanocore/compare/commits?targetBranch=refs%2Ftags%2Fkopanocore-8.7.20&sourceBranch=refs%2Ftags%2Fkopanocore-11.0.1&targetRepoId=1

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

@meyca
+1

fbartels

@meyca said in Kopano Core 8.7.20 Final:

Will this change be forwarded to 9.x, 10.x and/or 11.x? It seems, it has not been forwarded, yet.

I have answered this question in https://forum.kopano.io/post/19776, since you also asked the question there.

longsleep

@meyca

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.

@longsleep
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
Carsten

longsleep

@meyca

Yes, all backports become be part of a release/tag.

@longsleep said in Kopano Core 8.7.20 Final:

@meyca

Yes, all backports become be part of a release/tag.

@longsleep
Ok. I am not wrong. Thank you.

And the reason for not “releasing” or “tagging” this fix to 9.x and 10.x until now? When will this happen?