« Return to Thread: [trunk] Last API Changes for 0.3x/0.40 / close to a freeze...
Re: [trunk] Last API Changes for 0.3x/0.40 / close to a freeze...
by Daniel Gollub-3
::
Rate this Message:
On Thursday 09 April 2009 09:30:16 am Bjoern Ricks wrote:
> Hi
>
> here is a short status update for all people who are waiting for the
> next release ;-)
Great - thanks for keeping everyone up to date!
[...]
> >>
> >> [API] Common API interface pattern for list-implementations
> >> http://www.opensync.org/ticket/975
> >>
> >> Björn is working on that.
> >
> > still ongoing - expected to be complete soon.
>
> Done and committed in r5448. Now all list related interface will return
> a OSyncList. The returned OSyncList is always a shallow copy of an
> internal opensync structure/list and has to be freed in the application
> or plugin. Please be sure that osync_list_free is called on the returned
> list to avoid memory leaks.Björn, thanks for completing this!
>
> >> -
> >>
> >> [API] size_t/unsigned int review and cleanup
> >> http://www.opensync.org/ticket/974
> >
> > done for the public API - so not blocking anymore 0.39 milestone. Got
> > moved to 0.40
>
> Internal api still needs cleanup but it isn't blocking the next release.
> This should be a trivial task too.Right.
>
> >> -
> >>
> >> Make OSyncCapabilities and the use of Merger/Demerge format independent
> >> http://www.opensync.org/ticket/1084
> >>
> >> Still need to finish my "design" draft. As soon this is ready i'll drop
> >> a new mail about this. I already started to make some notes in the
> >> wiki... but it's incomplete. (This based on the previous discussion
> >> regarding "native capabilities", alternative to xmlforamt and stuff like
> >> that ..)
> >
> > This is still open ... i plan to invest today my time on that.
>
> The discussion is still ongoing. Daniel could you write a short mail
> about the current status and your planning?Still waiting for some comments on [RFC] Plugin specifc capabilities II
http://thread.gmane.org/gmane.comp.misc.opensync.devel/3787/focus=3818
Patrick, any chance to review/read/think about this mail?
>
> >> -
> >>
> >> Separate static and dynamic parts of plugin/member configuration
> >> http://www.opensync.org/ticket/1013
> >>
> >> I'm not quite sure if we still can do this without touching any API. If
> >> so this is not blocking 0.39.
> >
> > Still need to be clarified if this involves any API change. if not this
> > is not blocking 0.39
>
> I am not sure about this ticket and the current status. It was
> originally created by Henrik. So Henrik could you write some sentences
> about it?Actually i planned to take care about this once the capabilities issue is
fixed. IIRC Henrik is quite busy with other thing and doesn't have time right
now taking care about this. Maybe we should open this for other takers?
Btw. there are two missing from the 0.39 Roadmap:
[API] Check public interfaces for proper error reporting
http://opensync.org/ticket/1087
Björn, maybe something for you since you're our most talented API-Maintainer!
;)
[TRIVIAL][testsuite] tests/sync-tests/check_multisync.c unported/disabled
http://opensync.org/ticket/981
Ian started on this - but is unavailable to continue working on this. I highly
recommend to work on testcases like this to learn a lot from OpenSync
Internals and Engine - to become a OpenSync Guru ;)
Best Regards,
Daniel
--
Daniel Gollub Geschaeftsfuehrer: Ralph Dehner
FOSS Developer Unternehmenssitz: Vohburg
B1 Systems GmbH Amtsgericht: Ingolstadt
Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537
EMail: gollub@... http://www.b1-systems.de
Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg
http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
> Hi
>
> here is a short status update for all people who are waiting for the
> next release ;-)
Great - thanks for keeping everyone up to date!
[...]
> >>
> >> [API] Common API interface pattern for list-implementations
> >> http://www.opensync.org/ticket/975
> >>
> >> Björn is working on that.
> >
> > still ongoing - expected to be complete soon.
>
> Done and committed in r5448. Now all list related interface will return
> a OSyncList. The returned OSyncList is always a shallow copy of an
> internal opensync structure/list and has to be freed in the application
> or plugin. Please be sure that osync_list_free is called on the returned
> list to avoid memory leaks.
>
> >> -
> >>
> >> [API] size_t/unsigned int review and cleanup
> >> http://www.opensync.org/ticket/974
> >
> > done for the public API - so not blocking anymore 0.39 milestone. Got
> > moved to 0.40
>
> Internal api still needs cleanup but it isn't blocking the next release.
> This should be a trivial task too.
>
> >> -
> >>
> >> Make OSyncCapabilities and the use of Merger/Demerge format independent
> >> http://www.opensync.org/ticket/1084
> >>
> >> Still need to finish my "design" draft. As soon this is ready i'll drop
> >> a new mail about this. I already started to make some notes in the
> >> wiki... but it's incomplete. (This based on the previous discussion
> >> regarding "native capabilities", alternative to xmlforamt and stuff like
> >> that ..)
> >
> > This is still open ... i plan to invest today my time on that.
>
> The discussion is still ongoing. Daniel could you write a short mail
> about the current status and your planning?
http://thread.gmane.org/gmane.comp.misc.opensync.devel/3787/focus=3818
Patrick, any chance to review/read/think about this mail?
>
> >> -
> >>
> >> Separate static and dynamic parts of plugin/member configuration
> >> http://www.opensync.org/ticket/1013
> >>
> >> I'm not quite sure if we still can do this without touching any API. If
> >> so this is not blocking 0.39.
> >
> > Still need to be clarified if this involves any API change. if not this
> > is not blocking 0.39
>
> I am not sure about this ticket and the current status. It was
> originally created by Henrik. So Henrik could you write some sentences
> about it?
fixed. IIRC Henrik is quite busy with other thing and doesn't have time right
now taking care about this. Maybe we should open this for other takers?
Btw. there are two missing from the 0.39 Roadmap:
[API] Check public interfaces for proper error reporting
http://opensync.org/ticket/1087
Björn, maybe something for you since you're our most talented API-Maintainer!
;)
[TRIVIAL][testsuite] tests/sync-tests/check_multisync.c unported/disabled
http://opensync.org/ticket/981
Ian started on this - but is unavailable to continue working on this. I highly
recommend to work on testcases like this to learn a lot from OpenSync
Internals and Engine - to become a OpenSync Guru ;)
Best Regards,
Daniel
--
Daniel Gollub Geschaeftsfuehrer: Ralph Dehner
FOSS Developer Unternehmenssitz: Vohburg
B1 Systems GmbH Amtsgericht: Ingolstadt
Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537
EMail: gollub@... http://www.b1-systems.de
Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg
http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
signature.asc (204 bytes) « Return to Thread: [trunk] Last API Changes for 0.3x/0.40 / close to a freeze...
| Free embeddable forum powered by Nabble | Forum Help |
