From 7a42714eeac3f07baedb13359d94f1b010fe2ddf Mon Sep 17 00:00:00 2001 From: Patrick Ohly Date: Sun, 12 Nov 2006 12:46:22 +0000 Subject: [PATCH] # updates for 0.5 release git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@288 15ad00c4-1369-45f4-8270-35d70d36bdcd --- ChangeLog | 17 +++++++++++++++++ NEWS | 4 +++- 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 3b4f6bc3..0613739a 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,20 @@ +2006-11-12 Patrick Ohly + + * test/runtests.py: + added building of release packages, adapted to some more known server limitations + + * src/TestEvolution.cpp: + renamed testRefreshSync to testRefreshFromServerSync and added testRefreshFromClient + + * src/normalize_vcard.pl: ignore known limitations of Synthesis server + +2006-11-11 Patrick Ohly + + * NEWS, configure.in: 0.5 release + + * src/EvolutionContactSource.h, src/EvolutionSyncSource.h, src/EvolutionCalendarSource.cpp, src/EvolutionCalendarSource.h, src/EvolutionContactSource.cpp, ChangeLog: + messages about local changes are now logged as DEBUG and not INFO because they were confusing for users; now they are not visible in the final report + 2006-11-11 Patrick Ohly * src/EvolutionContactSource.h, src/EvolutionSyncSource.h, src/EvolutionCalendarSource.cpp, src/EvolutionCalendarSource.h, src/EvolutionContactSource.cpp, ChangeLog: diff --git a/NEWS b/NEWS index eb94d411..7754c8cb 100644 --- a/NEWS +++ b/NEWS @@ -1,4 +1,4 @@ -SyncEvolution 0.4 -> 0.5, 11.11.2006 +SyncEvolution 0.4 -> 0.5, 12.11.2006 ------------------------------------ * C++ client library revision "syncevolution-0-5": - added support for sending changes in smaller chunks @@ -7,6 +7,8 @@ SyncEvolution 0.4 -> 0.5, 11.11.2006 - time is printed with GMT offset so that a server admin in a different timezone can always figure out how a client log relates to events on the server + - special item keys as they might be stored in some calendars after + importing non-Evolution events are now properly supported * bug fix: in 0.4 it was necessary to manually configure the verDTD or the Funambol 3.0a server would choke on the invalid SyncML during the second synchronization with SyncEvolution; now this option is set