On 9/28/2026 6:57 PM, Tim Parenti via tz wrote:
From CBC Calgary, 4 September 2026. Some business owners in Alberta
are starting to notice disruptions and discrepancies in their digital
calendar and booking apps:
https://www.cbc.ca/news/canada/calgary/alberta-permanent-daylight-savings-businesses-calendars-9.7331872
One business owner said "[t]his feels like a secret Y2K that we're not
ready for, I think."
Those on this list will know that these discrepancies are handled in a
range of application-specific ways which are often not transparent to
the end-user, and that neither applications nor standards really
contemplate or allow for the definition of expected behavior when zone
definitions change. As such, these issues tend to crop up anytime a
timekeeping change is implemented with any less notice than the
typical leadtime with which folks are booking appointments.
The article mentions tz's role but misstates the date of release for
2026c, which contained Alberta's change, as 7 August instead of 8 July.
"(UTC-07:00) Pacific Time (British Columbia)" and "(UTC-06:00) Mountain
Time (Alberta)" have now appeared in my install of Windows 11 (25H2).
Perhaps life is better at the end of September than it was at the beginning.
