[Chandler-dev] a proposal to avoid user grief during 0.6 to 0.7 migration

[Mike Taylor]

During the last Platform working group meeting we discussed ways to 
avoid the following scenario:

The user is currently dog-fooding Chandler 0.6 and wants to try out the 
ultra-snazzy-cool changes that 0.7alpha2 delivers, so they download and 
run the installer/dmg/tarball.  During this process they receive the 
"hey, your current data schema is sooo 0.6" message and they select no 
so they can run Chandler 0.6 to backup their data.

It is at that point that we start getting tons of emails and IRC 
messages because Chandler 0.6 has been efficiently overwritten with the 
sparkly new 0.7 application.

doh!

One of the methods proposed at the meeting takes the simple route to 
solve the problem -- install Chandler 0.7 into a 0.7 labeled directory 
and default the repository to a 0.7 labeled profile directory.

The changes required would be to tweak the distribution script to 
create all install images using chandler_070 as the base directory and 
to prefix the profile search and default path with 070/

This process would continue until a properly automated upgrade method 
has been identified and tested.

Thoughts, counter-points, silly remarks?  This issue is being tracked 
by bug 5810.

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060503/de7c61a9/PGP.pgp