On Wed, 2007-09-05 at 13:48 +0200, Julien Kerihuel wrote:
> Hi List,
> 
> I'm currently trying to schedule libmapi-0.6 release and define
> libmapi-0.8 features/roadmap.
> 
> Now samba4-alpha1 is released, we can rely on this version rather than
> previous technology preview. We obviously need to test if everything is
> OK with OC, but except the libmapiadmin issue described below, there
> shouldn't be any problems.
> 
> We now have almost all the features we intended to provide in
> libmapi-0.6:
> 
> 1. New features:
> - FindRow
> - Copy and Move
> - IProfAdmin interface improvements (password outside profile)
> - Restrictions
> - Permissions and Rights
> - Public Folder support
> 
> 2. Very new (and initially not planned) features:
> - libmapiadmin: add/delete user
> - openchangepfadmin tool
> 
> 3. Objectives not reached:
> - Notification system support is not yet complete.
> - There has been no work on the binding system.
> 
> I think these new features are significant enough so we can safely plan
> to release libmapi-0.6 soon (based upon samba4-alpha1). In the meantime,
> some issues need to be discussed and some tasks need to be completed:
> 
>         - libmapiadmin and samba4/smb.conf global variable. There is a
>         bug that prevent libmapiadmin functions to work properly unless
>         a smb.conf file is created and unix_charset, dos_charset etc.
>         are set. Jelmer, I didn't yet have time to give is a closer
>         look, but is this issue solved in samba4-alpha1 or is there a
>         workaround I can use in mapiadmin_init to fix this?
> 
>         - permissions and rights. I agree with Dan we do need to improve
>         the current Role and Permissions management. Dan's proposal is
>         correct and it shouldn't take long to improve the existing
>         system. 
> 
>         - OC documentation: We need to review existing OC API, tools,
>         add necessary documentation and/or review existing one.
>         
>         - make test: Jelmer proposed to add a "make test" rule to the
>         build system. I think it is a really good idea and would
>         possibly require to rewrite/clean-up parts of the torture API so
>         we can automate the full process and have a clear coverage
>         overview.
>         
>         - LOG/DEBUG Dan's proposal: Should we implement it now and make
>         it available in libmapi-0.6 or plan its addition for
>         libmapi-0.8?

I also need to make a full review of our current MAPI_RETVAL_IF and
errno usage in libmapi. 

-- 
Julien Kerihuel
[EMAIL PROTECTED]
OpenChange Project Manager

GPG Fingerprint: 0B55 783D A781 6329 108A  B609 7EF6 FE11 A35F 1F79

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel

Reply via email to