Sorry for the amount of e-mails you may have received by now. No matter whether my patch will make it or not, I propose a lazy migration where our old custom `MOZ-` attributes stay untouched unless the date/time of an event or alarms attached to it are touched, editing the description of an event should not silently upgrade to VALARM. Backwards compatibility with older Thunderbird releases cannot be a concern forever, afaik there are no other users of the `MOZ-` style attributes. For clarity, I am talking about `X-MOZ-LASTACK`, `X-MOZ-SNOOZE-TIME` as well as `X-MOZ-SNOOZE-TIME-*`.
Bug 702206 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sorry for the amount of e-mails you may have received by now. No matter whether my patch will make it or not, I propose a lazy migration where our old custom `X-MOZ-` attributes stay untouched unless the date/time of an event or alarms attached to it are touched, editing the description of an event should not silently upgrade to **VALARM**. Backwards compatibility with older Thunderbird releases cannot be a concern forever, afaik there are no other users of the `X-MOZ-` style attributes not capable of also parsing modern **VALARM**. For clarity, I am talking about `X-MOZ-LASTACK`, `X-MOZ-SNOOZE-TIME` as well as `X-MOZ-SNOOZE-TIME-*`.