6:17 a.m.
Hi!
Okay, long time now see, eh, write. Quick recap:
* SyncEvolution 1.0 beta 1 released, development keeps us busy.
1.0 beta 1 turned out to be fairly stable, but there were bug
fixes (see below). Lots of new features in "master", so consider
compiling that if you want to follow what we are doing.
* 0.9.2 released. Ove Kaaven made it available for Maemo,
including a calendar backend that he wrote.
* Went to FOSDEM last weekend and gave two talks. Slides can be
viewed on our site, video of the Lightning Talk will be posted
by FOSDEM later. See
http://syncevolution.org/blogs/pohly/2010/fosdem-2010
Noteworthy new issues potentially affecting users:
* The packages provided by Ubuntu and Debian did not contain
proper timezone support. Use the packages from syncevolution.org
to work around this (Debian bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565720, Ubuntu
bug https://bugs.launchpad.net/bugs/509032)
* 1.0 beta 1 cannot do Bluetooth sync via GUI because transport is
missing in syncevo-dbus-server (MB #9436, patch pending)
* 1.0 beta 1 has an issue with unintentionally enabling sources
created for one peer in another (MB #9329); when configuring
a peer using the "server" shorthand for a
"server@other-context", properties from the default context were
copied into that other context (MB #9338)
* The Horde Groupware server gets confused by our device ID and
applies workarounds for old, broken Funambol clients to us,
which break calendar sync (MB #9347). Using such device IDs was
necessary at one point for Funambol (wouldn't support multiple
instances otherwise), but that no longer is the case, so can be
fixed by renaming the device ID.
Comment for distributors: there's a new README.packagers file. Please,
consider compiling and packaging the GNOME Bluetooth Panel plugin that
is included in the lastest SyncEvolution source code (not yet in 1.0
beta 1).
Development (by week basically, starting end of last year):
* Yongsheng: D-Bus implementation of client/server interaction for
dialogs in the UIs (MB #6376), used for interactive password
requests, database restore (MB #8144), auto-termination of D-Bus
server and tracking of clients (MB #7710), added support for
X-SKYPE (MB# 8948)
* Congwu: finished "super datastore" (= merged calender/todo),
force slow sync on server-side when requested, discussed and
worked on configuration and pairing of phones (MB #7838/7089),
dealt with feedback about phone syncing (Nokia 6600, N900, N85),
analysis of sync stack in Maemo 5/N900, fixes for OBEX
transport, datastore aliases (MB #7871), don't resend initial
message of sync (MB#8758), removed hard dependency on CPPUnit
header files
* Raji: http_proxy env variable support when using libsoup[-gnome]
(MB #8177), recreating full name when lost on server (MB #5664)
* Patrick: implemented handling of unexpected slow syncs in the
client (MB #2416), Android port, some more Oracle testing
* Yongsheng: syncevo-dbus-server automatic termination when idle
(MB #7711), fixed IO spinner support in D-Bus server,
investigated different sync solutions improved D-Bus testing (MB
#9065), fixed handling of normalized config names in logdir code
(MB #8350)
* Congwu: template handling for SyncML clients, searching for
right template via fuzzy LCS string match and custom code,
assist QA with Bluetooth testing, GNOME Bluetooth panel plugin,
presence detection
* Patrick: CPPUnit header file dependencies (MB #9149), code
merging and distribution fixes, configuration option and
infrastructure for handling unexpected slow syncs (MB #9156,
#2416), normalization of config names when saving to disk (MB
#8350), documentation update for 1.0 (MB #8497), more flexible
support for backend-specific XML configs, avoid exceptions
during normal run, fixed reporting of local errors (MB #8757)
and partially successful syncs (MB #7755), improved printing of
report (MB #2069), added Goosync and Oracle templates, timeouts
for unresponsive clients (MB #7710), "syncevolution --status"
local item counts empty (MB #9097)
* Jussi: fixes for unified configuration dialog, slow sync and
emergency handling
* Raji: investigated timezone conversion issues with Outlook
meeting invitations (MB #4815)
* Yongsheng: finished auto-termination of syncevo-dbus-server (MB
#7711), updated test-dbus.py (MB #9065, may still overwrite
developer's data MB #9332), started to provide more information
via D-Bus API (password MB #9169, first sync flag MB #8729)
* Congwu: presence detection for HTTP
* Patrick: command line screwed up shared properties when using a
shorthand notation for peers in the non-default context (MB
#9338, already broken in 1.0 alpha, found to late for 1.0 beta),
adding sources affects other peers in same context (MB #9329,
found by QA in 1.0 beta), fixed --disable-bluetooth (MB #9260),
fixed source code compatibility with libbluetooth2 and 3 (MB
#9289),
* Jussi: several GTK GUI updates, for example restore from backup
* Yongsheng: GetConfig() includes real passwords (MB #9169),
return first-time sync information via GetReports (MB #8729),
fix for test-dbus.py so that it no longer overwrites normal
local databases (MB #9332), GetConfig() support for Bluetooth
peers (MB #9216, some improvements and debugging left to do, see
MB #9576)
* Congwu: presence detection via ConnMan for HTTP and Bluetooth,
GNOME Bluetooth Panel plugin in SyncEvolution
* Patrick: fix for CheckSource() and virtual sources (MB #9535),
fixes for logdir naming, database dumps now use less disk space
thanks to hard-linking, database comparisons are faster,
database comparison is more intelligent about previous dump (all
part of MB #7708), included Congwu's GNOME Bluetooth Panel
plugin in the SyncEvolution distro (MB #7089), split up XML
config into parts which can be extended/replaced by users and
synchronized with Synthesis upstream (MB #7712)
* Jussi: device configuration, lots of fixes and polishing now
that QA is testing the redesigned UI
--
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.