We are continuing to push on toward the 0.8 release candidate. In that
vein, I'd like to make a special plea for testing. We are about to check
in the code that will update the timezone database. Once that happens,
we need you to do two things:
* TEST: We could really use your help in testing this. You know your own
time zone far better than we do, so make sure your calendar switches
into and out of summer time (or doesn't switch at all) at the
appropriate dates for this year.
* BACKUP:If you have been running the 0.8 nightly builds, then you MUST
backup your local (non-network) calendars (export them to ICS) BEFORE
upgrading to a build with this change in it. The details are in
bugzilla, but if you are running some of the 0.8pre builds, then this
change might break your calendar when you update to the latest nightly.
**What if I am running 0.7 (or earlier)?**
In that case, you are fine. You should be able to upgrade to 0.8 with no
problems. Of course, it is always a good idea to periodically backup
your calendars anyway. This issue occurs because we don't support
upgrades between nightly versions, only between released versions of the
That said, we know a number of early adopters have already made the
switch to 0.8pre builds and we want them to be aware of this potential
Does this affect people who never explicitly set timezones when creating
events and who have never accepted invites or imported events from other
people? My OS' and Lightning's timezones are always the same
Clint, on Bugzilla  you say the following:
"So, the point here is that for some users on some builds of our
nightlies, the timezone upgrade will fail. It will cause the
application to throw and it will no longer startup properly. "
So my question before I upgrade to a nightly with this fix in:
I have backed-up my calendars, but what should I do when the above
described scenario occurs? Can I still startup Thunderbird? If so,
should I un-install Calendar, re-install it and create new calendars and
import my backups?
If TB does not start at all, what do I do than?
Warning people is great, but without telling them what can be done to
fix the problem if it occurs is not really helpfull. (or maybe it is
just me and all other nightly testers already know how to recover from
such a problem.)
Thanks for the quick update. It seems like it is less of an issue that i
thought it would be. When you mentioned 'will not start not properly' I
expected the worst. Happy to hear it is 'just' the calendar.
Thanks for the warning anyway. It could have turned out different.