On Mon, 2011-10-17 at 12:18 +0200, Patrick Ohly wrote: > SyncEvolution 1.2 - now with CalDAV/CardDAV > =========================================== > > The major new feature of the 1.2 release is support for non-SyncML > protocols in general and CalDAV/CardDAV in particular.
[...] > http://syncevolution.org/blogs/pohly/2011/syncevolution-12-released For those who don't follow the syncevolution.org news feed: I also posted a summary of the nightly test runs which produced the 1.2 release: http://syncevolution.org/blogs/pohly/2011/syncevolution-12-released#comment-525 Let me cut-and-paste here, for a version with hyperlinks go to the blog post: ----------------------------------------------------------------- Nightly test results for this release are archived here: * all tests * Google Calendar after fixing a bug in test driver The interesting tests are under the "head-testing-amd64" directories. The other directories include compilation and sanity tests. Tests ran under valgrind. No issues left with memory handling; occasionally __strcasestr_sse42() leads to false positive. Note that these tests were adapted so that they ignore known limitations of each peer. The README files bundled with the release document some of those. What follows is an explanation of things visible or found while testing SyncEvolution 1.2. Google CalDAV: * stand-alone detached recurrences cannot be accessed, SyncEvolution workaround only works for some cases * meetings removed by SyncEvolution - not sure yet whether this is better fixed on the server or client side * cannot updated/delete meetings although the organizer: SyncEvolution is allowed to create an event, but then cannot update or remove it * cannot remove detached recurrence: breaks the testLinkedItemsRemoveNormal tests Overall Google Calendar syncing works well (I'm using it myself) as long as one does all meeting scheduling in the Google web interface. Google Contacts (SyncML): * no issues, but not very complete either (many properties not supported by Google, for example BDAY) Apple Calendar Server, DAViCal: * no issues, full support for iCalendar 2.0 and vCard 3.0 Yahoo CalDAV/CardDAV: * works well, when it works; unfortunately the number of requests per 24 hour period is so limited that the tests cannot complete without running into a 503 "Service Unavailable" error Synthesis: * works fine except for one issue: X- extensions with \; in the value return the value with a double semicolon (issue with vCard 3.0 -> vCard 2.1 in the server?) Funambol, Mobical (aka Freedroid): * work fine except for occasional load issues Memotoo: * server regression around tasks, other failures need to be investigated (contact slow sync incomplete in testTwinning, contact extensions) -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
