Hi Jared, > As of right now, the office calendar is still broken; as soon as > everyone's up to speed, I think we should delete and recreate the > offending event to get back on track.
In r14984 I checked in a fix for bug 9849 and bug 9856, the Chandler side of this problem. I don't know if we'd already deleted the offending event on the office calendar, but my updated Chandler synced the office calendar just fine, and after this revision we shouldn't be creating more offending modifications. In that checkin I also made a change to the way modifications are serialized, which in the long run should result in fewer spurious conflicts on recurring events. But in the short term for collections shared by several people, if people using recent and old versions of Chandler sync, they may ping pong changes back and forth. This shouldn't be a big deal (because we're changing data that's ignored except when calculating diffs), but it may make syncing collections with lots of recurring events a little slower until everyone syncing those collections upgrades to a post 14984 revision. So, dogfooders should upgrade when we've got a new checkpoint. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
