1
SyncEvolution 1.1.99.1 -> 1.1.99.5, 13.07.2011
2
==============================================
4
Release 1.1.99.5 is the first release candidate for 1.2. It has gone
5
through a long stabilization period and thus is suitable for normal users.
7
The major new feature of the 1.2 release is support for non-SyncML
8
protocols in general and CalDAV/CardDAV in particular. ActiveSync
9
support is in development. These protocols are implemented as backends
10
which are combined with other backends by SyncEvolution in a so called
11
"local sync". The GTK sync-ui does not yet support configuring
12
non-SyncML protocols. See the README.rst and man page for more
13
information on how to use the new feature via the command line.
15
Properties not supported by SyncML servers can now be preserved
16
locally in two-way synchronization (BMC #15030). This depends on
17
information about what properties a SyncML server supports ("CtCap"),
18
which is typically not provided by servers. SyncEvolution contains a
19
copy of that information for Google Contacts (BMC #15029).
21
Akonadi backend and KWallet support were merged. They are not included
22
yet in syncevolution.org binaries. To use them compile from source.
24
The configuration format was updated to solve a conceptual problem
25
inherited with the legacy property names: the "type" property had
26
multiple, sometimes conflicting roles. For example, setting the
27
preferred data format for sync with one peer might have changed the
28
backend selection for some other peer (BMC #1023). Now
29
"backend/databaseFormat/syncFormat/forceSyncFormat" replace
30
"type". "type" is still accepted by the command line as alias.
32
Old configurations can still be read. But writing, as it happens
33
during a sync, must migrate the configuration first. In contrast to
34
earlier, more experimental releases in the 1.2 series, 1.1.99.5 and
35
later automatically migrate configurations. The old configurations
36
will still be available (see "syncevolution --print-configs") but must
37
be renamed manually to use them again under their original names with
38
older SyncEvolution releases.
41
* syncevo-http-server was enhanced considerably. See http://syncevolution.org/wiki/http-server-howto
42
* support NetworkManager API >= 0.9 (BMC #19470)
43
* Sync mode is recorded when running in SyncML server mode (BMC #2786).
44
* syncevo-dbus-server automatically stops when some of its libraries
45
are updated and restarts if auto-syncing is on (BMC #14955).
46
* Using the --sync-property and --source-property command line options is
47
optional, just specifying the property assignment is enough.
48
* Added support for Buteo, mKCal and QtContacts in MeeGo.
49
Buteo and mKCal were removed again from MeeGo, so the code
50
is obsolete. The QtContacts backend may be still be useful
51
to access items via that API, but for syncing on MeeGo
52
the normal EDS backend is used since MeeGo reverted back
53
to EDS as PIM storage.
54
* code cleanup and various minor fixes/improvements, see ChangeLog
57
SyncEvolution 1.1 -> 1.1.1, 26.12.2010
58
======================================
60
Maintenance release, in particular improving syncing with phones.
61
There was a bug that could cause all kinds of weird behavior after
62
a failed sync with a phone, so updating is highly recommended.
64
* Synthesis engine: fixed a corruption issue in internal meta data which
65
caused duplicates and other problems in a pretty indeterminstic way;
66
apparently caused by failed syncs (BMC #11044).
68
* Synthesis engine: recurrence rules with end date now sent correctly to phones (BMC #11241).
70
The RRULE property was not encoded correctly previously during the
71
iCalendar 2.0 -> vCalendar 1.0 conversion. Events with recurrence count
72
were okay. Probably also affected SyncML servers without iCalendar 2.0
75
The fix was confirmed to work with Nokia phones. It also helps with Sony Ericsson
76
phones, but at least the t700 still has a problem: depending on the phone's
77
time zone, it repeats the event for one day too long (BMC #10092).
79
* Synthesis engine: fixed broken time zone information when sending to phone;
80
previously that broke sending calendar updates to Nokia phones (BMC #9600).
82
iCalendar 2.0 time zone definitions imported from libical were not
83
encoded correctly in vCalendar 1.0 items as sent to phones. Nokia
84
phones accepted such data when part of a new event, but rejected
87
* Synthesis engine: shorter TZIDs, might help N900 calendar (BMC #6680).
89
The shorter TZIDs will be included in iCalendar 2.0 data exported
90
by libsyntesis and thus SyncEvolution. This change is motivated primarily
91
by the observation that the N900 calendar storage can handle TZID=<location>,
92
but not TZID=/softwarestudio.org/Tzfile/<location>.
94
* ScheduleWorld: disable configuration template because service has shut down.
96
The template is only hidden from the GTK sync-ui, but remains in SyncEvolution
97
for the time being because it is referenced in several places.
99
* Evolution CalDAV: added workaround for "must sync twice" (BMC #10265)
101
The Evolution CalDAV backend seems to update its data when closing the
102
database, not when opening it. As a result, syncevolution had to be run
103
twice to see all data changes. The workaround is to open the database
104
twice at the start of the sync. This is done for all calendar databases,
105
regardless of which backend they use, in case that some other (yet unknown)
106
backend needs the same workaround.
108
* GTK sync-ui: workaround for "Sync Now" button not reacting to online
109
status changed (BMC #9949).
111
* Changed slow sync handling. Some users have complained about getting
112
duplicated contacts (BMC #10081). The exact reason is not known (no
113
useful logs provided yet), but it might be due to using "duplicate"
114
as resolution strategy during slow syncs.
116
This caused slightly different contacts to be duplicated instead of
117
merging the two copies, reasoning that "no data loss" is better than
118
"duplicates". This release switches to a mode where the engine
119
tries harder to avoid duplicates by merging data if modification
120
time stamps are available for contacts (usually they are). When fields
121
differ, the more recent data is kept.
123
* convert absolute alarm back to relative (BMC #11233)
125
Experiments show that at least Nokia phones (and thus perhaps also
126
Mobical.com) interpret a fixed alarm as "repeat alarm with the same
127
relative offset as on first occurrence". The same transformation to
128
relative alarm times is applied whenever the transformation to
129
absolute alarm is enabled for a peer.
131
* Sony Ericsson: enable conversion to absolute alarm times (BMC #10092)
133
Like Nokia and Mobical.net, Sony Ericsson phones also seem to be unable
134
to deal with relative alarm times - verified with t700.
136
* Sony Ericsson C510: workaround for SyncML violation
138
The phone does not sent identifiers for the target database;
139
using the source identifier as fallback allows a sync to
142
* Fixed a regression affecting users who had created a config
143
with SyncEvolution < 1.0. Using the config worked once, then
144
failed with "No configuration for ... found". Users must
145
manually remove the empty "peers" directory inside their
146
affected configuration, the fix only makes configs without that
147
directory usable again (BMC #9381).
149
* Removed obsolete workaround for older mKCal calendar storage.
150
* Fixed error message in QtContacts backend.
151
* Same SYNCEVOLUTION_DEBUG code as in master branch.
152
* Some updates to synccompare, including a workaround for a Perl
153
bug seen on Debian Testing with Perl 5.10.1-16 (Perl panic).
154
* Fix compilation of syncevo-dbus-server with libnotify 0.7.0 (BMC #10453).
155
* Fixed compilation on Debian GNU/Hurd (no MAX_PATH, Mac OS X confusion).
1
158
SyncEvolution 1.0.1 -> 1.1, 26.10.2010
2
159
======================================
added
removed
NEWS
