maryjane/syncevolution
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

# updates for 0.5 release

Browse source 
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@288 15ad00c4-1369-45f4-8270-35d70d36bdcd
This commit is contained in:
Patrick Ohly 2006-11-12 12:46:22 +00:00
parent d325c9316a
commit 7a42714eea
2 changed files with 20 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
ChangeLog
View file

@ -1,3 +1,20 @@
2006-11-12 Patrick Ohly <Patrick.Ohly@gmx.de>
* 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 <Patrick.Ohly@gmx.de>
* 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 <Patrick.Ohly@gmx.de>
* src/EvolutionContactSource.h, src/EvolutionSyncSource.h, src/EvolutionCalendarSource.cpp, src/EvolutionCalendarSource.h, src/EvolutionContactSource.cpp, ChangeLog:

4
NEWS
View file

@ -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