Quote:
Originally Posted by Ryan Lederman Yeah, this is as-expected, as we had to redesign the entire timezone functionality. We may include an upgrade notes box at the end of the upgrade that explains. |
I think you should consider it a bug. It affects timestamps throughout the application. It made all the activity for the four hours before I updated to appear to be in the future, and when I fixed my TZ, all my psuedocron tasks appeared to have fired four hours in the future.
I'm hoping that the fallout will be minimal since I did the install at the end of our workday, and I caught it pretty quickly, but it wasn't a good feeling to have to leave it in that state and have to hope that by morning it would right itself. (I did not have time to investigate the problem(s) carefully.)
Note that I had more problems appear after I set the time zone, since I'm at -400 this time of year, whereas I expect those who are in positive offsets would resolve most of there issues just by setting the TZ.
Perhaps you could add a step to set the TZ in the upgrade script?