Re: [Kolab-devel] Upgrade report 3.1 to 3.2 on Debian Wheezy

On Tuesday 11. March 2014 17.31.12 Daniel Hoffend wrote:
> 
> I haven't had anytime to do any more tests in the last weeks. But when I
> followed the mailing list I see lots of people complaining about the new
> cyrus version. With changes like the cyrus ldap lookup patch it just
> doesn't feel like a "drop-in" update for a groupware.

I saw the cyrus-imapd stuff enter the picture and although it is probably 
offering nice features that we will all eventually benefit from, bumping the 
version seems to have caused compatibility issues. Maybe this is where the 
community (and other entities) get to show their value, but I feel that this 
kind of thing stretches the community rather thin.

> tbh (and this is just my opinion).
> 
> The upgrade procedures feels a bit rough and more like "testing in the
> wild". Kolab Team is announcing a new 3.2 version (and people trust you
> and think it's stable). When you look closer it feels really unstable
> and untested. It began with 100% cpu look of kolabd, the missing upgrade
> commands on debian packages (which i fixed in obs)

Is there a Web-viewable summary of these fixes?

Paul