@markvnl said in Builing kopano for Centos:
Is it like it’s Friday afternoon-beer time and you decide it is about time to push a release out? – just kidding
Why not, that doesn’t sounds too bad ;-)
Version tagging is a bit different for each project. In WebApp a new version is tagged once a sprint has concluded, for Groupware Core we tag (with the exception of x.y.80-99, since they are reserved for nightly, beta and rc versions) when we are confident it contains what we want in it. There is a delay between tagging and an actual binary release to customers since here we do final qa checks. qa could keep a release back (as it happened with 8.6.x until 8.6.2) in case its not declared “fit for customers”. Tags will be kept in that case and the dance begins again once a new version is tagged.
In regards to specific versions of dependencies and buildtools. We usually try to work with the versions being available in the distributions we support. if that is not possible we compile and maintain these dependencies ourselves. So its a recommendation to check which packages and versions we provide for any custom builds
As for gcc 4.8.5. There are concrete plans to retore gcc 4.x in general, the only reason holding back for the moment is that this is still required for Debian 8, once this distribution is out of support there is no reason for us anymore to optimize for newer versions.