[Cosmo-dev] Cosmo 0.6.1 release status

[Morgen Sagen]

On May 10, 2007, at 9:35 AM, Aparna Kadakia wrote:

> Morgen,
> qacosmo will be upgraded with a new build today. Not everyone will  
> have a chance to sync their collections before the upgrade.
> What are the repercussions if they don't ?

They're going to be republishing their collections based on what is  
in their dump file.  I put in step 1 so that what is in their dump  
file will match the most recent data on the server.  If nothing has  
changed on the server since their last sync, they won't lose anything.


> Will the reload of the old dump and ics files still work?

Yes.  Again, I recommend also exporting to .ics before wiping out  
their Chandler repos for any calendars that are important, just in case.


> On May 10, 2007, at 8:33 AM, Morgen Sagen wrote:
>> 1) Give people warning that they should sync their collections  
>> using their current version of Chandler one last time so their  
>> local repositories match what is on the server
>> 2) Users should dump their data using "File > Dump Items to  
>> File...".  Note: you might also want to export to .ics file(s)  
>> just in case the dump/reload doesn't work
>> 3) Shut down qacosmo, upgrade it, wiping the db
>> 4) Get the latest version of Chandler from Trunk and run it
>> 5) "File > Reload items from File..." (or import any .ics file(s)  
>> that were exported in step 2)
>> 6) For any collection in the sidebar that is shared, do "Share >  
>> Unsubscribe"
>> 7) Publish collections to new version of qacosmo