[Cosmo-dev] Re: etag change
mikeal at osafoundation.org
Fri Apr 20 11:29:27 PDT 2007
> Let's expand the steps a bit:
> 1. Chandler user has been syncing with osaf.us running Cosmo 0.6.0.1
> 2. Chandler user should sync all changes to osaf.us, just prior to
> Cosmo 0.6.1 upgrade of osaf.us; an announcement should go out
> telling people not to make local changes until after they have
> performed step #4
> 3. osaf.us gets upgraded from 0.6.0.1 to 0.6.1
> 4. Chandler user syncs, unfortunately pulling down every item, but
> if they were careful not to make local changes between #2 and #4,
> they won't lose anything
> 5. Chandler user unsubscribes (or unpublishes if daring) from dav
> collection (leaving the collection in the local Chandler repository)
> 6. Chandler user sets up "Chandler Hub Sharing" (aka morsecode)
> account in their Accounts dialog
> 7. Chandler user republishes collection using morsecode account,
> gets back new "pim" urls to hand out to people
> How's that sound?
If a user is going to set up a Chandler Hub Sharing account and
republish anyway why do they need to do the resyncs using the old
sharing format and worry about losing local changes?
I think an easier set of steps would be.
1. Disable DAV based sharing account prior to osaf.us upgrade.
2. After osaf.us upgrade setup "Chandler Hub Sharing" account and test.
3. Republish all collections you wish to share on osaf.us
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20070420/1bd4f52e/PGP.pgp
More information about the cosmo-dev