New triggers are physical, old ones are temp, when downgrading users will have both. We should either - build a time machine - fix all released versions - make new triggers temp The first option requires too much time. The second option requires a long work of syncing across branches and cannot guarantee the result for all cases. The third option could have a really ignorable hit on Ts, but it's largely easier, faster and safer to do. so we'll probably do that. At least till Storage will have some migration stuff :(
Actually, spending time on the first option would be feasible, since once done I could go back and recover time. But I guess drivers won't be happy in the meanwhile.
this is blocking our Places branch merge.
Assignee: nobody → mak77
Status: NEW → ASSIGNED
blocking2.0: --- → ?
Created attachment 492968 [details] [diff] [review] patch v1.0
Attachment #492968 - Flags: review?(dietrich)
Comment on attachment 492968 [details] [diff] [review] patch v1.0 looks fine, r=me
Attachment #492968 - Flags: review?(dietrich) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b9
We should relnote in beta9 that it cannot downgrade to beta7 or previous beta versions (downgrading to 3.6.x or beta8 is fine instead).
You need to log in before you can comment on or make changes to this bug.