We've found that our alpha 4 support during DAV->EIM migration is iffy.
I don't have a full grasp of the issues, but I'd thought it'd be
helpful to flag the basic issue.
There are a couple observations that feed into this.
1) I, and others, can't restore a fair number of our collections from
osaf.us into alpha 4 for testing.
2) One user, Davor, who has been a steady alpha 4 user, filed a new bug
9252 during migration testing today, where his osaf.us shares would not
restore into 20070518.
What I guess is going on is there are event syntax/semantics issues
between alpha 4 and trunk. Essentially everyone at OSAF, through long
use, has had their osaf.us data updated to a form compatible with trunk.
A user like Davor who hasn't upgraded ever since alpha 4, has their
osaf.us data in a format that trunk can't read.
The converse also appears to be true (trunk-compatible osaf.us data
can't be restored into alpha 4) but that's less of a concern (there's
not even a bug filed because we don't really care, I think).
As of right now, we have no workaround. If we choose to do anything
about this situation, we may need to fire up alpha 4, and publish some
shares to a test account to be able to replicate outside Davor's account.
Next steps are to see if there's are any comments to this thread.
Beyond that, I'll probably work with Philippe and Sheila to determine if
we want to do Chandler Desktop work in trunk or perhaps just tell alpha
4 users to use ics export/import exclusively.
-- Jared
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
