Hi, all

I'm thinking we should roll a 0.7.4.1 on behalf of the following bug:

<https://bugzilla.osafoundation.org/show_bug.cgi?id=11823>
Couldn't migrate 0.7.3 to 0.7.4 on MacOSX

I'm busy rolling a new chandlerdb in the trunk (since otherwise future 0.7.4 -> 0.7.5 upgraders would be affected by this). Once the tarballs are available, this should make rolling a 0.7.4.1 candidate a straightforward process.

Pros of rolling the release:
- People who download 0.7.4 and have run a past Chandler get a better user experience (i.e. no feedback dialog; they get pointed at migration instructions, etc.). - The instructions for migration will become valid again (the missing step with this bug in place is that you have to erase your repository yourself once you've exported your data).

Cons:
- If you upgrade from 0.7.4 to 0.7.4.1, you'll need to migrate your data (even though, under the hood, nothing has really changed).

Any thoughts/comments/objections?

--Grant

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to