If a repository exists, we have to be creating a new one for a reason,
right?
- If the reason is "--create", I don't think the dialog should appear (I
use --create all the time, and want it to indicate that I want whatever
existing repository I have to be overwritten by a new one)
- If the reason is because Chandler has noticed that the existing
repository is old, then sure, put up the dialog. (I think the existing
repository could be "old" not just because it's as old as alpha4 - it'd
be "old" if the schema version doesn't match.)
Are there other reasons?
...Bryan
Mike Taylor wrote:
Currently the Upgrade Notification dialog will be triggered if the
following condition is met:
Does a repository from a previous Chandler version exist and we
are creating a new repository
Remember I'm asking about what needs to be done for Preview
First I want to make sure that is the only condition in everyone's
mind about what triggers the notification - true?
Second I want to point out that currently the only version we could
realistically expect a user to migrate from is 0.7alpha4 - true?
Just wanting to make sure I have all the facts and that all
assumptions are on the table.
thanks,
---
Bear
Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org
[EMAIL PROTECTED]
http://code-bear.com
PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
------------------------------------------------------------------------
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
