Liam, Thank you for your posting; it is good to document these things. My definition of the Battle River Time Option Area is the union of following 4 areas: - City of Lloydminster - subdivision 6 of School Division 203 (includes Maidstone) - subdivision 7 of School Division 203 (includes Marshall and Hillmond) - subdivision 8 of School Division 203 (includes Marsden and Neilburg) I believe this definition matches the original boundaries of Battle River School Division 60, and I believe it…
On Wed, 28 Oct 2026 at 13:48, Bratty, Michael (Vancouver) via tz < tz@iana.org> wrote: > The name of the new Pacific Time zone is PCT. > Thanks for writing in. The discussion on province-specific abbreviation neologisms has been had several times over. For fairly comprehensive details on our current rationale for avoiding introducing these abbreviations at the systems level for now, please see this earlier thread: https://lists.iana.org/hyperkitty/list/tz@…
https://globalnews.ca/news/12124122/quebec-government-time-change/ https://www.cbc.ca/news/canada/montreal/end-time-change-parti-quebecois-9.7399165 Quebecers will turn back their clocks for the last time this weekend, according to the Parti Québécois (PQ). The party hopes to table a bill in the coming months to abolish the time change. A PQ spokesperson told CBC that the party plans to hear from experts during a parliamentary committee hearing on adopting permanent daylight time or standard…
The 2026f release of the tz code and data is available. This release is prompted by Cuba’s decision to stay on UTC-04 this winter, which has a practical effect starting 2026-11-01 at 02:00. This release contains the following changes: Briefly: Cuba will not fall back 2026-11-01; stays on -04 through 2027-11-07. No more leap seconds, and leap second tables no longer expire. Improve 1965/1966 data for Brazil. Changes to future timestamps Cuba will not fall back to -05 on 2026-11-01 and instead…
Hello, I would like to share some extra information about the "Lloydminster area". Soon it will be mainly of historical interest. However, currently it may help anyone carrying out a system migration. The extent of the "Lloydminster area" was not clear from Wikipedia or the City of Lloydminster website. Many articles incorrectly refer to the city limits, while others refer to a vague "area around Lloydminster". Wikipedia is of course being updated frequently at this time to reflect the new…
FYI The governing authority of British Columbia announced “the change would legally establish a new “Pacific Time” zone set at UTC−7. “. The legislative amendment was introduced in 2019 and the change announced March 2 2026. The name of the new Pacific Time zone is PCT. BC Gov News Time Zone Database Release 2026b *** WORLEY GROUP NOTICE *** "This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this…
According to Media-Government Relations in Regina[1], residents of Lloydminster "have long been used to running on 'Lloydminster time'"[1]. I hope we can resist the temptation to create a new Zone just for Lloydminster merely so that locals can see on their screens the time zone abbreviation "LMT". [1]: https://www.saskatchewan.ca/government/news-and-media/2026/april/30/saskatchewan-replaces-the-time-act-welcomes-alberta-to-central-standard-time
On Tue, 27 Oct 2026 at 13:13, Heitor David Pinto via tz wrote: > The government of Saskatchewan issued the order for the Time Act, 2026, > which replaces the earlier Time Act, to come into force on 30 October 2026. > https://publications.saskatchewan.ca/#/products/130175 > This act sets UTC-6 all year in the whole province, including > Lloydminster, the last part of America/Edmonton to officially make this > change. Thanks; it also presumably makes it much more straightforward for the area…
On Tue, 27 Oct 2026 at 01:47, Paul Eggert via tz wrote: > The first one implements your suggestions. The second one rewords our data > to better match the wording of older Brazilian decrees (unlike your > suggestions, this doesn't change any timestamps). Thanks; I'd come to broadly similar conclusions. However, it's worth noting that phrases like "até 31 de março", even when defined in law to "include" the last day, still carry some ambiguity — is that last "legal day" that is considered the…
Awesome, thanks for the update! Em ter., 27 de out. de 2026 às 02:46, Paul Eggert escreveu: > Thanks for the corrections. I installed the attached patches to the > development repository on GitHub. The first one implements your > suggestions. The second one rewords our data to better match the wording of > older Brazilian decrees (unlike your suggestions, this doesn't change any > timestamps). These patches should appear in the next TZDB release, which > should be quite soon due to the Cuba…
Thanks for the corrections. I installed the attached patches to the development repository on GitHub. The first one implements your suggestions. The second one rewords our data to better match the wording of older Brazilian decrees (unlike your suggestions, this doesn't change any timestamps). These patches should appear in the next TZDB release, which should be quite soon due to the Cuba situation.
The government of Saskatchewan issued the order for the Time Act, 2026, which replaces the earlier Time Act, to come into force on 30 October 2026. https://publications.saskatchewan.ca/#/products/130175 This act sets UTC-6 all year in the whole province, including Lloydminster, the last part of America/Edmonton to officially make this change.
On 2026-10-26 08:07, Alysha Saville via tz wrote: > We are hoping to have these changes implemented before the November 1 automatic fall back to minimize confusion for residents and allow us to provide advance guidance (if required) on preventing devices from automatically reverting by one hour. Thanks, I think we're already OK from the TZDB viewpoint, as users in RDEK and Golden can continue to use the equivalent of TZ="America/Edmonton" as they did before. As long as they update their devices…
On 10/26/2026 4:05 PM, Paul Eggert via tz wrote: > On 2026-10-26 11:27, Almaz Mingaleev via tz wrote: >> Fiji did a similar thing and Paul speculatively cancelled DST altogether >> back then. >> Is this a bad candidate for doing the same? > > As I vaguely recall, the Fiji government's 2022 announcement didn't > say what the plans were after 2022/2023, and out-of-band information > suggested that the change would more likely be permanent than not. In > contrast Cuban government's announcement…
On Oct 23, 2026, at 5:45 AM, David via tz wrote: > I have attached a technical analysis of the Windows Architecture as it relates to the Manitoba Standard Time TZ update and a enterprise readiness guide I put together, incorporating this discussion. > > Any feedback is appreciated. This is for internal use only. Internal to whom and what? This is a public mailing list....
On 2026-10-26 11:27, Almaz Mingaleev via tz wrote: > Fiji did a similar thing and Paul speculatively cancelled DST altogether > back then. > Is this a bad candidate for doing the same? As I vaguely recall, the Fiji government's 2022 announcement didn't say what the plans were after 2022/2023, and out-of-band information suggested that the change would more likely be permanent than not. In contrast Cuban government's announcement stated the intention to resume DST switching in November 2027, so…
Hi folks, Advice is to run a manual update check. Although I normally delay updates by ~4 weeks, Windows 10 ESU Tuesday Patch only did .NET, and something that updated the TZVersion from 2026-0002 to 2026-0003, in HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Time Zones, reg value 0x07ea0003. So I just started a manual update check, which is now *slo-o-o-w-w-wly* downloading the 2026-10 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5126657). Downloaded…
Fiji did a similar thing and Paul speculatively cancelled DST altogether back then. Is this a bad candidate for doing the same? On Mon, 26 Oct 2026 at 18:23, Tim Parenti via tz wrote: > > On Mon, 26 Oct 2026 at 13:57, James Bellaire via tz wrote: > >> On 10/26/2026 1:42 PM, Robert Bastian via tz wrote: >> >> Given that they are planning on returning to standard time next November, >> I'd ask for this to not be modeled as a change to a different offset >> (UTC-4) (as has been done with zones…
On Mon, 26 Oct 2026 at 13:57, James Bellaire via tz wrote: > On 10/26/2026 1:42 PM, Robert Bastian via tz wrote: > > Given that they are planning on returning to standard time next November, > I'd ask for this to not be modeled as a change to a different offset > (UTC-4) (as has been done with zones that have moved to *permanent* DST), > but instead as staying on DST (UTC-5+1). > > At this point it's impossible for CLDR to get changes out to devices > before Nov 1, and formatting would mess up…
On 10/26/2026 1:42 PM, Robert Bastian via tz wrote: > Given that they are planning on returning to standard time next > November, I'd ask for this to not be modeled as a change to a > different offset (UTC-4) (as has been done with zones that have moved > to /permanent/ DST), but instead as staying on DST (UTC-5+1). > > At this point it's impossible for CLDR to get changes out to devices > before Nov 1, and formatting would mess up if this was modeled as > UTC-4. No changes to…
On Mon, 26 Oct 2026 at 13:29, Tuenvio via tz wrote: > On October 24, 2026, the Cuban authorities announced that daylight saving > time would remain in effect until November 7, 2027, suspending the usual > return to standard time scheduled for November 1, 2026. > Although your email lacked a link to verifiable information, I was able to find the following on the Cuban government's main web portal: http://www.cuba.cu/otras/2026-10-25/cuba-mantendra-horario-de-verano-hasta-noviembre-de-2027/69459…
Given that they are planning on returning to standard time next November, I'd ask for this to not be modeled as a change to a different offset (UTC-4) (as has been done with zones that have moved to *permanent* DST), but instead as staying on DST (UTC-5+1). At this point it's impossible for CLDR to get changes out to devices before Nov 1, and formatting would mess up if this was modeled as UTC-4. No changes to CLDR are required if returning to standard time is just skipped this winter. On Mon,…
News Article https://en.cibercuba.com/noticias/2026-10-24-u1-e74-s27061-nid343708-cuba-mantendra-horario-verano-noviembre-2027-retrasara On 10/24/2026 7:53 PM, Tuenvio via tz wrote: > Dear Time Zone Database Maintainers, > > I am writing to report an urgent time zone update issue concerning Cuba. > > On October 24, 2026, the Cuban authorities announced that daylight > saving time would remain in effect until November 7, 2027, suspending > the usual return to standard time scheduled for November…
Hello, I am writing to try to ensure that information regarding time observance changes in the East Kootenay region of BC is provided to the necessary organizations. The Regional District of East Kootenay (RDEK) Board, the Town of Golden Council and the Columbia Shuswap Regional District Board (for Electoral Area A) have both made decisions to cease semi-annual time changes and remain permanently on Mountain Daylight Time. For context, I have provided a map below from the National Research…
From: Ana Bobillo Since 2026c, OPENAT_TZDIR uses O_RESOLVE_BENEATH only when privileged, but tzloadbody still skipped its scan for non-terminal ".." components whenever OPENAT_TZDIR and O_RESOLVE_BENEATH were both nonzero, a leftover from when openat always used O_RESOLVE_BENEATH. So on platforms like FreeBSD that have O_RESOLVE_BENEATH but lack O_REGULAR, an unprivileged program compiled with -DOPENAT_TZDIR opened a TZ setting like "../file" or "/usr/share/zoneinfo/../file" without the…
Thanks for installing the fix. > I didn't see use of uninitialized transition times in the unpatched > code. Can you give a scenario when that happened? It needs 32-bit time_t (I used -Dtime_tz=int32_t) and a TZif file whose version 2+ data has these three transitions, out of order: -2**40, 2**40, -2**40 + 1 (types 0, 1, 2) In the first loop of tzloadbody at 48e83594: i = 0: -2**40 is kept, clamped to TIME_T_MIN: types[0] = 1, ats[0] = TIME_T_MIN, timecnt = 1. i = 1: 2**40 > TIME_T_MAX is…
Thanks for reporting the problem. I installed the attached three patches to the development repository on GitHub. The first is minor refactoring nearby; the second fixes the 32-bit checking to be as strict as the 64-bit (the main point of your bug report); the third looks forward to tightening up the checking even more in the future. On 2026-10-21 20:21, Ana Bobillo via tz wrote: > + than 64 bits. Formerly, with 32-bit time_t such a file could cause > + these functions to use uninitialized…
David, Thanks very much for this thorough analysis. I always learn more about Windows. In this case the files in C:\Windows\Globalization\Time Zone. Oh sure enough, that's where those are. Mine are not updated: timezones.xml "" I cannot comment on the many IT procedures you are addressing. I'm just a guy working alone. I do have one comment, perhaps obvious to this audience: systems and applications that rely directly on TzDb and the TzDb TZif file sets must be sure to update and distribute the…