Question about upgrading cyrus-imapd in Kolab 3.3 Updates

[Daniel Hoffend]

> I just don't have a clue if something else has changed from git
> version 2.5~dev2014082101-0~kolab1 to
> cyrus-imapd_2.5~dev2014120901-0~kolab1. Since it's the same major
> version I guess it's mostly bugfixes and not a major feature
> enhancement. And with Kolab 3.4 incoming soon(tm) according to it's 6
> month release cycle i guess this version of cyrus will be shipped with
> 3.4 anyway.

I'm looking at the git log of cyrus 
http://git.cyrusimap.org/cyrus-imapd/log/

lots of things have changed from August to the december snapshot. If you 
find the correct commit that fixes this segfault I would be happy to 
accept the patch. But taking a fully new snapshot just to fixes one bug 
is kinda risky.

Apart from that Kolab 3.4 is sheduled for next month (was released last 
year around mid february). Then everything what's in Kolab:Dev will be 
pushed to Kolab:3.4 anyway and become (announced) stable. I guess 
testing Kolab:Dev should have higher priority (right now) to make the 
upcoming release more secure rather then having an upcoming upgrade 
desaster.

-⁠-⁠
Daniel