Legend: D=Done, ?=Unknown, n/a=Not Applicable, N=Developer does not want to do it because there are higher prios, R=compiles and runs (though can be unusable or unstable).

+

−

==Links==

+

==Development==

+

Much of the infrastructure of KDE PIM has been moved to kdepimlibs module as a framework for all KDE applications. Therefore we have two main modules within the KDE SVN: '''kdepim''' and '''kdepimlibs'''. The latter contains code that provides public APIs.

Kontact is the primary [http://kolab.org/ Kolab] client. There are different release cycles for the Kolab clients and for KDE, and therefore there are so-called <i>enterprise</i> branches in SVN where the Kolab versions are maintained. Changes in the enterprise branches are regularly merged back to SVN trunk.

+

The enterprise branches are maintained by [http://www.klaralvdalens-datakonsult.se/ KDAB].

Resources

Development

Much of the infrastructure of KDE PIM has been moved to kdepimlibs module as a framework for all KDE applications. Therefore we have two main modules within the KDE SVN: kdepim and kdepimlibs. The latter contains code that provides public APIs.

Current development focus as of January 2009 is on the Akonadi service and porting existing applications to Akonadi and KMime and other frameworks.

Enterprise branches

Kontact is the primary Kolab client. There are different release cycles for the Kolab clients and for KDE, and therefore there are so-called enterprise branches in SVN where the Kolab versions are maintained. Changes in the enterprise branches are regularly merged back to SVN trunk.
The enterprise branches are maintained by KDAB.