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… Found some article (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/how-windows-manag...) but they declare 8 weeks change duration there… С/у Andrey Kazakevich From: Andrey Kazakevich Sent: Thursday, January 25, 2024 9:38 AM To: 'Tim Parenti' <tim@timtimeonline.com>; Dauren Sarsenov <daur88@gmail.com> Cc: tz@iana.org; Alexey Sharkov (KZ) <e-Alexey.Sharkov@homecredit.kz> Subject: RE: [tz] Kazakhstan to shift from UTC+6 to UTC+5 Hi, everyone! Thanks for quick reply and such detail information! Will wait required for us change… Thanks again! С/у Andrey Kazakevich From: Tim Parenti <tim@timtimeonline.com> Sent: Thursday, January 25, 2024 1:20 AM To: Dauren Sarsenov <daur88@gmail.com> Cc: tz@iana.org; Alexey Sharkov (KZ) <e-Alexey.Sharkov@homecredit.kz>; Andrey Kazakevich <Andrey.Kazakevich@erg.kz> Subject: Re: [tz] Kazakhstan to shift from UTC+6 to UTC+5 ВНИМАНИЕ: Данное письмо направлено извне ERG. Не открывайте ссылки и вложения, если вы не знаете отправителя и не уверены в безопасности содержимого. (Combining replies to a few similar messages.) On Wed, 24 Jan 2024 at 13:08, Dauren Sarsenov via tz <tz@iana.org<mailto:tz@iana.org>> wrote: There is an upcoming timezone change I want to inform you about. In Kazakhstan we are moving away from UTC+6 to UTC+5 across all areas of the country. The change is effective at 00:00 1 march 2024. Thanks; we were made aware of this change for Kazakhstan on 19 January. See: https://mm.icann.org/pipermail/tz/2024-January/033566.html https://mm.icann.org/pipermail/tz/2024-January/033570.html On Wed, 24 Jan 2024 at 13:07, Alexey Sharkov (KZ) via tz <tz@iana.org<mailto:tz@iana.org>> wrote: 3-1. Акиматам городов Астаны, Алматы, Шымкента, Акмолинской, Алматинской, Жамбылской, Карагандинской, Костанайской, Павлодарской, Северо-Казахстанской, Туркестанской, Восточно-Казахстанской областей и областей Абай, Жетісу, Ұлытау в ночь с 29 февраля 2024 года на 1 марта 2024 года (в 00:00 часов) перевести местное время на 1 час назад.". For all Kazakhstan zones set local time back 1 hour night of February 29, 2024 to March 1, 2024 (at 00:00 hours) Zone Asia/Almaty Zone Asia/Qyzylorda Zone Asia/Qostanay Zone Asia/Aqtobe Zone Asia/Aqtau Zone Asia/Atyrau Zone Asia/Oral Our understanding is that this change only affects the eastern portions of the country represented by Asia/Almaty and Asia/Qostanay, and not the other zones as those areas already observe UTC+5 so will not be changing their clocks. This appears to be reflected in the locations listed in the quoted legal text. On Wed, 24 Jan 2024 at 13:08, Andrey.Kazakevich--- via tz <tz@iana.org<mailto:tz@iana.org>> wrote: How I can know when this change will be released? You may want to consider subscribing to the low-traffic tz-announce mailing list at https://mm.icann.org/mailman/listinfo/tz-announce which announces new tzdb releases as they come out. There is no set schedule for a new release, as this is a volunteer project; however, we are obviously now aware that one is needed ahead of 1 March. So you can plan for a new release reasonably soon, once we've allowed folks some time to test and comment on the pending changes. Have you some tracking or history of changes in database? The main development copy of the database is kept on Github at https://github.com/eggert/tz/commits/main where you can find the upcoming change for Kazakhstan already in place: https://github.com/eggert/tz/commit/95a16c87f21c4643055482429dad921357a630c9 -- Tim Parenti

OK, understood. Thank you very much! С/у Andrey Kazakevich From: Tim Parenti <tim@timtimeonline.com> Sent: Thursday, January 25, 2024 9:39 PM To: Andrey Kazakevich <Andrey.Kazakevich@erg.kz> Cc: tz@iana.org; Rustam Sirotkin <Rustam.Sirotkin@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@erg.kz<mailto:Andrey.Kazakevich@erg.kz> <Andrey.Kazakevich@erg.kz<mailto:Andrey.Kazakevich@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/D... Found some article (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/how-windows-manag...) 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

On Fri, 2 Feb 2024 at 03:19, Andrey.Kazakevich@erg.kz < Andrey.Kazakevich@erg.kz> wrote:

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?

I'm not sure I'm understanding the question. At a minimum, your servers will need to take whatever time zone definition updates are available to them, and you'll want to ensure that those using tzdb have got at least version 2024a. It may take a while longer until those updates are ready for any given system, though. A tz release like yesterday's is just an initial step in a distribution process that involves various vendors of operating systems, programming libraries, and telecommunications infrastructure, all repackaging our release for use within their own respective ecosystems. Depending on what your servers are doing, you may need updates from any or all of these sources which are all downstream of us. This is why we typically recommend several months' notice in advance of time zone changes whenever possible. And as a reminder, Microsoft uses a completely separate process from us for disseminating time zone updates to Windows devices. So if your servers are Windows servers, we can't really help other than to point again to "(UTC+05:00) Ashgabat, Tashkent" as a potential workaround. -- Tim Parenti

On 2024-02-02 12:17, Tim Parenti via tz wrote:

On Fri, 2 Feb 2024 at 03:19, Andrey Kazakevich wrote:

...

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?

I'm not sure I'm understanding the question.  At a minimum, your servers will need to take whatever time zone definition updates are available to them, and you'll want to ensure that those using tzdb have got at least version 2024a.

It may take a while longer until those updates are ready for any given system, though.  A tz release like yesterday's is just an initial step in a distribution process that involves various vendors of operating systems, programming libraries, and telecommunications infrastructure, all repackaging our release for use within their own respective ecosystems.  Depending on what your servers are doing, you may need updates from any or all of these sources which are all downstream of us.  This is why we typically recommend several months' notice in advance of time zone changes whenever possible.

And as a reminder, Microsoft uses a completely separate process from us for disseminating time zone updates to Windows devices.  So if your servers are Windows servers, we can't really help other than to point again to "(UTC+05:00) Ashgabat, Tashkent" as a potential workaround.

You can see if any MS products support any time zone update by checking: https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/bg-p/D... and apply any available updates to the affected products, otherwise you will have to use the suggested workaround above to switch to that or an equivalent time zone you may already use, on February 29 24:00/March 1 00:00. Different products may require different time zone selections to make the desired change. For example, each OS, MS Windows, Outlook, Exchange, Azure, WSL, Java, database software, may each require their own updates and time zone setting. -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry