diff options
author | Patrick Ohly <patrick.ohly@intel.com> | 2011-02-04 21:34:09 +0100 |
---|---|---|
committer | Patrick Ohly <patrick.ohly@intel.com> | 2011-02-04 21:34:09 +0100 |
commit | ed0300a32eab8b7549a853d07fa0ad4ca4363e39 (patch) | |
tree | 5961fb32713fbd943e41dd1cf5a8739292f7525d /NEWS | |
parent | 637e80f91f063984d24f9162f9ab6c51994cb93b (diff) |
added 1.1.99.2
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 27 |
1 files changed, 27 insertions, 0 deletions
@@ -1,3 +1,30 @@ +SyncEvolution 1.1.1 -> 1.1.99.2, 04.02.2010 +=========================================== + +Major internal changes. Supports synchronization between two +SyncEvolution backends ("local sync"). + +The configuration format was updated to solve a conceptual problem +inherited with the legacy property names: the "type" property had +multiple, sometimes conflicting roles. For example, setting the +preferred data format for sync with one peer might have changed the +backend selection for some other peer (BMC #1023). Now +"backend/databaseFormat/syncFormat/forceSyncFormat" replace +"type". "type" is still accepted by the command line as alias. + +Old configurations can still be read. But writing, as it happens +during a sync, must migrate the configuration first. 1.1.99.2 is an +experimental version and does not migrate configurations +automatically, as the final 1.2 release will do. The error 22005 +indicates that the user has to accept the backward-incompatible config +change. The command line prints instructions; basically do +"syncevolution --migrate @default". + +The old configurations will still be available (see "syncevolution +--print-configs") but must be renamed manually to use them again under +their original names. + + SyncEvolution 1.1 -> 1.1.1, 26.12.2010 ====================================== |