Thoughts on Installers/Data Migration

Original 0.7 goal

• Facilitate upgrade of 0.6 and 0.6.1 -> 0.7 easily
• Only calendar data

What has changed

• #1: Staging of Dashboard
  • Originally the experimental dashboard was a goal for 0.7, but now that 0.7 is turning into the Beta - it's a goal for some pre-0.7 milestone ie: Alpha4.
  • Having the dashboard assumes that users will have more than just calendar data - tasks, emails etc.
  • Do we need to have a migration path for Alpha4-AlphaX-0.7?

• #2: Cosmo Demo Data
  • Another migration path we haven't talked about is when data is wiped from Cosmo Demo.
  • Should there be an easy way for users to get going again and reconnect with all their shares?
  • Does this have to be a goal in 0.7?
  • Open Question: When are we going to have an reliable data migration path for Cosmo-Cosmo releases?

Current situation - as of Alpha2

• User installs new version of Chandler
  • A new separate profile directory is created - new repository - 0.7 directory
  • Users can run their old version of the app and export calendars.
  • Each published share has to be restored individually.
  • Re-subscribed to each share using the original URLs.

• Wipe out data on Cosmo Demo
  • Run old Chandler
  • Unsubscribe and republish all old shares individually.
  • Delete and resubscribe to all subscribed to shares - when we get new urls
  • Non shared data should be preserved in the repository

What do we want to have happen?

-- SheilaMooney - 20 Jun 2006