On Thu, 12 Nov 2026 at 23:46, Brian Inglis via tz <[email protected]> wrote:
> In zonenow.tab (current time correct only going forward) on 2026-11-01 > > America/Vancouver was merged into America/Phoenix > America/Edmonton was merged into America/Mexico_City > America/Winnipeg was merged into America/Jamaica > > as those other zones have had those offsets for longest, and/or have larger > populations than the legacy Canadian zones Stepping in quickly to correct a potential misapprehension here— these changes to zonenow.tab do NOT in any way mean the Canadian zones are "legacy" zones, and "merged" is really not the best verb here. zonenow.tab serves a specific and limited purpose for those who need to compile for devices which do not care about divergences in timekeeping prior to the present, or "now". Prior to the Canadian jurisdictions' changes being announced this year, the entires in question were previously coalesced in this list with America/Los_Angeles, America/Denver, and America/Chicago, respectively, since they had been forecast to continue North American DST into the indefinite future like these regions. Once a divergence was expected but had not yet occurred, these needed their own entries in zonenow.tab to reflect their unique futures from that point. Now that that time has passed, their predicted futures are identical to those of other zones, so they have been coalesced in this list once again. This only affects zonenow.tab, which again is only intended for this limited purpose. The zones themselves still retain their histories, and this change does not affect them directly or imply that they are "legacy" in any way. -- Tim Parenti
