Hello! Busy times... ;-) Merged all pending patches for improving interoperability with more servers (Mobical, Memotoo) into master branch in preparation for 0.9.1. As is often the case, the testing with Memotoo found several issues in the server, which were fixed quickly. Message resending suffered from one problem with misbehaving servers (endless loop with Funambol-based servers), which we have a work around for now. Synthesis has reviewed and merged all of our patches, too. Translations for 0.9/Moblin 2.0 in translate.moblin.org are now done on a maintenance branch, so we made our string changes for 0.9.1 on the master branch. We'll continue to work towards 0.9.1 on master for another week or so before releasing a snapshot and starting testing. The open issues for 0.9.1 are (most important first): * Congwu, 3427 - poor usability with network interruption: resend messages * Yongsheng, 3604 - command line: use keyring * Congwu, 6127 - workaround for 200 vs 201 status codes + Replace instead of Add * Jussi, 5871 - unsupported and unavailable data categories (Google calendar/task/memo) * Congwu, 6181 - Package SyncEvolution core as a library for third party developers * Memotoo + Yongsheng, 5635 - test and support Memotoo * Jussi, 5717 - sync UI needs to set an icon for its window * Jussi, 5219 - Add a Service with 200 chars of name, syncevolution-dbus has corewatcher Some of these have patches pending or just need testing, so there is some work left for me, besides writing the release notes ;-) During the face-to-face in London Jussi, Nick, Patrick, Tom Counihan (Intel's representative at GENIVI) talked about sync. It was a very productive meeting: lots of ideas for next steps and things to implement... In general, the wish list for 1.0 increased instead of decreased during the meeting. Regarding sync : we identified that automatic syncs are expected soon, because they make sync really useful in the Moblin usage models. Manual intervention should only be necessary when something went wrong. We were already working towards that goal (EDS API changes, sync server without GUI, recovery mode), but we didn't have it on our feature list for SyncEvolution 1.0. The biggest gap is in the GUI. My proposal is to work towards a 1.0 alpha with the features as planned so far (minimal changes in GUI, direct device-to-device sync), then re-evaluate whether we release it as 1.0 or continue adding the missing features. Development: * Yongsheng: keyring support (#3604), nightly testing, Memotoo interoperability * Congwu: article about extending SyncEvolution for the SDK, libsyncml patching for testing with OBEX, outgoing OBEX connections, Alert 222 loop detection. * Jussi: UI D-Bus proposal * Patrick: UI D-Bus proposal refinement, partial implementation in new syncevo-dbus-server, investigated build failure of SyncEvoluion 0.9 in Moblin trunk (root cause: invalid type in libsoup, reported and resolved now) Noteworthy new issues: * Users have reported problems with the Horde (server sends invalid XML, WBXML works) and eGroupware (doesn't support WBXML, sync does not complete) servers. Currently we are not testing against those. -- 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.