Hi! It's been a while that I sent a project status update... and no-one has complained about that. Are these kind of summary emails useful? Answer with "yes" and as a reward you'll get more of them in the future ;-) What should be summarized? One reason for not writing earlier was that I felt that the major news items (like SyncEvolution 0.9.1) were public knowledge anyway. The other reason was that development continued at full speed, leaving no time to stop and contemplate what had been achieved. So, without further ado: * SyncEvolution 0.9.1 released. Some issues in it where found, but nothing fatal and nothing that cannot be worked around [1] * Reorganized feature plan for SyncEvolution 1.0. It's not visible in the Bugzilla overview [2] because we kept several issues open, but enough of this already works so that we can probably call it a 1.0 alpha next week without being laughed at. * Direct synchronization with a phone via Bluetooth works - sort of. It works well enough to determine that this particular phone SyncML implementation is crap. * obexd 0.19 includes the plugin which redirects SyncML connection requests and data into SyncEvolution 1.x. [1] http://bugzilla.moblin.org/buglist.cgi?query_format=advanced&short_de... [2] http://bugzilla.moblin.org/showdependencytree.cgi?id=7892&hide_resolv... -- 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.