[Kolab-devel] Kolab Server 2.2.1 moves ahead

[Fabio Pietrosanti (naif)]

My compliments for the very good work done!

I am also seeing progress in Debian Package development that would allow 
a greater community to quickly install and use kolab on Debian systems.

One question: There's a delivery date for Kolab 2.2.1?

Fabio Pietrosanti

Gunnar Wrobel wrote:
> Hi!
>
> Just a short note about the Kolab Server 2.2.1 progress:
>
> p at rdus finished the development activities for this Kolab Server 
> version last week. Thus we move into testing and bug fixing now. There 
> should be betas available soon.
>
> What are notable changes in Kolab Server 2.2.1:
>
>   - The Kolab web client upgrades to horde-webmail-1.2 (+ a big Kolab 
> specfic
>     patch).
>   - Support for attachments as described by the Kolab format (leads to 
> photo
>     support in the address book as well as attachments to contacts).
>   - SyncML support for contacts and events.
>   - DIMP: AJAX based "dynamic" web client (horde)
>   - MIMP: mobile mail client (horde)
>
> In addition there are changes concerning the Kolab free/busy system as 
> well as the Kolab mail filters:
>
>   - Removal of kolab-filter, kolab-freebusy, as well as the code in 
> php-kolab
>     and replacement by upstream PEAR packages released via 
> http://pear.horde.org
>
> The main focus of this release is stabilization of the Kolab web 
> client and associated with this a consolidation of the Horde libraries 
> we use within the Kolab Server. While this does not bring much new 
> functionality I believe it provides us with a sound basis for the next 
> three years (as far as I can preview this period yet).
>
> The fact that most of the Kolab code has been moved upstream now has 
> several important side effects:
>
>  1) A single implementation of the Kolab concepts and thus a significant
>     reduction in code duplication.
>  2) Improved code quality.
>  3) phpUnit based unit testing for all Kolab specific modules.
>  4) Clean package releases based on PEAR.
>
> I realize that point 4) means a lot of new work for the native ports 
> but I'm convinced that this approach will reduce the maintenance 
> workload in the long run. It will also bring the different 
> distributions closer together as we have a clear reference point now.
>
> Cheers,
>
> Gunnar
>
> Cheers,
>
> Gunnar
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel