After updating the ical2eas and eas2ical conversion paths and some of
the SyncEvolution test cases, all of the eas_event source tests pass.
However, there are some open questions/gaps:
1. removing Exceptions as part of an Update (aka removing a
detached recurrence) is ignored by Exchange (BMC #22849)
2. support by Exchange for all-day events is poor (BMC #22780)
3. the ical2eas code only works if there is a parent event (BMC
If anyone has some bright idea or suggestions how 1 and 2 can be solved,
then I am all ears. The last one is a fairly obvious gap in the code,
but first I need to check for the right way to represent detached
recurrences without parent.
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.