[Kolab-devel] Changes to master branch

[Jeroen van Meeuwen (Kolab Systems)]

Mathieu Parent wrote:
> Hello,
> 

Hi Mathieu,

> 2011/4/16 Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com>:
> > - split out the kolab schema, because that is a dev/release cycle of its
> > own completely (backwards, forwards compatibility, deemed stable in the
> > very long-term, should not be changed lightly, etc.)
> 
> This is an opportunity for "kolab/issue3488 (kolabSharedFolder and
> kolabGroupOfNames should be AUXILIARY)"
> 

It does open up the ability to change the schema both incrementally as well as 
through KEPs for the more likely intrusive "major" development cycle changes, 
indeed.

Seeing as how kolab/issue3488 is linked with kolab/issue3343, as well as 
cross-domain ACLs, and future features of Kolab may provide it the ability to 
use more then one root dn (not to say 'more then one authn/authz database'), 
as well as potential impact on the current hosted- branch for the codebase, 
please allow me to give this some thought and get back to you.

Thanks for pointing this one out!

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110416/ed6ffcaa/attachment.html>