[tz] Kazakhstan to shift from UTC+6 to UTC+5

Andrey.Kazakevich at erg.kz Andrey.Kazakevich at erg.kz
Fri Feb 2 08:18:23 UTC 2024


Hi, guys!
As we can see an update in TZ DB was released yesterday (2024a (Released 2024-02-01)).
And I see that our timezone (Asia/Almaty) figured with future change there.
Does it mean that we don’t need to do TZ changes on our local corporate servers if they are using Asia/Almaty TZ at this time? Time will swap automatically or how it will be?

С/у Andrey Kazakevich

From: Tim Parenti <tim at timtimeonline.com>
Sent: Thursday, January 25, 2024 9:39 PM
To: Andrey Kazakevich <Andrey.Kazakevich at erg.kz>
Cc: tz at iana.org; Rustam Sirotkin <Rustam.Sirotkin at erg.kz>
Subject: Re: [tz] Kazakhstan to shift from UTC+6 to UTC+5

ВНИМАНИЕ: Данное письмо направлено извне ERG. Не открывайте ссылки и вложения, если вы не знаете отправителя и не уверены в безопасности содержимого.


On Wed, 24 Jan 2024 at 22:52, Andrey.Kazakevich at erg.kz<mailto:Andrey.Kazakevich at erg.kz> <Andrey.Kazakevich at erg.kz<mailto:Andrey.Kazakevich at erg.kz>> wrote:
Sorry, guys, another question – most of devices in our corporate environment are using (Astana +06:00) timezone in Microsoft Windows OS (Win10/11, Win Server 2019/2022).
Have you some information how are they changing their list of timezones? What is process in their global list…

We are not involved with Microsoft's process for time zone data, no.  Once they do announce a change, it will likely end up on their blog where they document their DST and time zone updates at:
https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/bg-p/DSTBlog

Found some article (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/how-windows-manages-time-zone-changes/ba-p/3852632) but they declare 8 weeks change duration there…

Yes, it's a complex process to propagate time zone updates to devices around the world.  It's why we recommend at least a year's notice ahead of changes whenever possible.  Because this change is so soon, it is quite likely that some devices won't receive updated time zone definitions in time.

As a workaround, users may need to consider temporarily using Asia/Aqtobe or Asia/Tashkent on devices that use tzdb, although these will mishandle timestamps before the change.  On Windows, a similar approach may look like using "(UTC+05:00) Ashgabat, Tashkent", as I believe that's already the correct choice in western portions of Kazakhstan.

--
Tim Parenti
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tz/attachments/20240202/181367ad/attachment.htm>


More information about the tz mailing list