Kazakhstan (all parts) switching to UTC+5 on March 1, 2024
Kazakhstan (all parts) switching to UTC+5 on March 1, 2024 https://www.gov.kz/memleket/entities/mti/press/news/details/688998?lang=ru
Thanks for the heads-up. I've installed the attached patch to the development repository. This means our latest release will be wrong for eastern portions of Kazakhstan in just under 6 weeks, so we'll need a new one soon. -- Tim Parenti On Fri, 19 Jan 2024 at 13:25, Zhanbolat Raimbekov via tz <tz@iana.org> wrote:
Kazakhstan (all parts) switching to UTC+5 on March 1, 2024
https://www.gov.kz/memleket/entities/mti/press/news/details/688998?lang=ru
On 2024-01-19 11:15, Tim Parenti via tz wrote:
I've installed the attached patch to the development repository.
Thanks, I installed the attached further patches to pacify 'make check' for zonenow.tab, and to update some related commentary and diagnostics. As you can see, zonenow.tab needs care and feeding when these sorts of changes are made. The file will need further changes after the clocks change in Kazakhstan in March (as well as in Greenland later in March). This sort of thing is one reason I put off creating zonenow.tab for so long.... I also wrote Kazakhstan's ambassador to the US, asking when the clock changes would become official. Today's announcements make it sound like unofficially it's going to happen but there is at least one more legal hoop to jump through. It'd be helpful if that were cleared up. I also referred the ambassador to our usual guideline <https://data.iana.org/time-zones/tz-link.html#coordinating> of a year's notice of changes, and suggested that Kazakhstan's government warn cell phone users that on March 1 they can set their phones to Tashkent time as a workaround if the phones haven't yet been updated automatically.
Hi, Here is an official link to the Prime Minister's website (published today Sat, 20 Jan 2024): https://primeminister.kz/ru/decisions/19012024-20 Seems PM signed the decree yesterday. Paragraph 3 and 3.1 states to switch to +5 to all oblasts (states). Thank you On Sat, Jan 20, 2024 at 3:56 AM Paul Eggert <eggert@cs.ucla.edu> wrote:
On 2024-01-19 11:15, Tim Parenti via tz wrote:
I've installed the attached patch to the development repository.
Thanks, I installed the attached further patches to pacify 'make check' for zonenow.tab, and to update some related commentary and diagnostics.
As you can see, zonenow.tab needs care and feeding when these sorts of changes are made. The file will need further changes after the clocks change in Kazakhstan in March (as well as in Greenland later in March). This sort of thing is one reason I put off creating zonenow.tab for so long....
I also wrote Kazakhstan's ambassador to the US, asking when the clock changes would become official. Today's announcements make it sound like unofficially it's going to happen but there is at least one more legal hoop to jump through. It'd be helpful if that were cleared up.
I also referred the ambassador to our usual guideline <https://data.iana.org/time-zones/tz-link.html#coordinating> of a year's notice of changes, and suggested that Kazakhstan's government warn cell phone users that on March 1 they can set their phones to Tashkent time as a workaround if the phones haven't yet been updated automatically.
-- Zhanbolat Raimbekov
On 2024-01-19 22:42, Paul Eggert via tz wrote:
Thanks for the link. I installed the attached patch to the TZDB commentary.
0001-Add-Kazakhstan-PM-s-decision.patch
From 1fe97024d56b5d4ef7d3513a83c14803f0b5fcae Mon Sep 17 00:00:00 2001 From: Paul Eggert<eggert@cs.ucla.edu> Date: Fri, 19 Jan 2024 21:26:22 -0800 Subject: [PROPOSED] =?UTF-8?q?Add=20Kazakhstan=20PM=E2=80=99s=20decision?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit
* asia: Add link to prime minister’s decision (thanks to Zhanbolat Raimbekov). --- asia | 1 + 1 file changed, 1 insertion(+)
diff --git a/asia b/asia index bca31abc..2b74b8a3 100644 --- a/asia +++ b/asia @@ -2461,6 +2461,7 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # Kazakhstan (all parts) switching to UTC+5 on March 1, 2024 #https://www.gov.kz/memleket/entities/mti/press/news/details/688998?lang=ru # [in Russian] +# (2024-01-20):https://primeminister.kz/ru/decisions/19012024-20 # # From Alexander Krivenyshev (2024-01-19): # According to a different news and the official web site for the Ministry of -- 2.40.1
Good choice of effective date - chances of time zone errors compounding inevitable leap day errors, for those still not yet up to date ;^% on the contents of Pope Gregory XIII's papal bull from 1582! Nitpick: As they are repeating 2024-02-29 23.00-24.00 so 2024-03-01 is delayed an hour in regions observing UTC+6, should this decree not be going into effect on 2024-02-29 rather than 2024-03-01, assuming the translation below is correct? Google Translation: "20 January 2024, 09:00 Decree of the Government of the Republic of Kazakhstan dated January 19, 2024 No. 20 On amendments to the Decree of the Government of the Republic of Kazakhstan dated November 23, 2000 No. 1749 “On the procedure for calculating time on the territory of the Republic of Kazakhstan” The Government of the Republic of Kazakhstan DECIDES : 1. Introduce the following changes to the Decree of the Government of the Republic of Kazakhstan dated November 23, 2000 No. 1749 “On the procedure for calculating time on the territory of the Republic of Kazakhstan”: paragraph 1 should be stated as follows: "1. Establish that on the territory of the Republic of Kazakhstan, the calculation of time reproduced, stored and transmitted by the State primary standard of time and frequency of the Republic of Kazakhstan is carried out according to the international system of time zones.”; paragraphs 3 and 3-1 should be stated as follows: "3. Apply the 5th time zone to the entire territory of the Republic of Kazakhstan. 3-1. Akimats of the cities of Astana, Almaty, Shymkent, Akmola, Almaty, Zhambyl, Karaganda, Kostanay, Pavlodar, North Kazakhstan, Turkestan, East Kazakhstan regions and Abay, Zhetisu, Ulytau regions on the night of February 29, 2024 to March 1, 2024 (at 00:00 hours) set local time back 1 hour." 2. The Ministry of Culture and Information of the Republic of Kazakhstan to inform the population about the procedure for calculating time on the territory of the Republic of Kazakhstan. 3. This resolution is subject to official publication and comes into force on March 1, 2024, with the exception of paragraph 2 of this resolution, which comes into effect from the date of its signing. Prime minister Republic of Kazakhstan A. Smailov" [I just noticed that the Julian date of issue of the papal bull was ante diem sextum Kalendas Martias 1581 (O.S.) which is the day doubled (bissextile) in Roman calendar leap years: a.d.bisVI Kal.Mart. Also, as the implementation date was set for 1582-10-05, 7 months later, at a time when messages were passed by ship, horse, and foot, this project should adopt 7 months as the official minimum notice and maximum allowed implementation time frame for time zone changes as of 2024-02-25 ;^> ] -- 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
On 2024-01-20 08:37, brian.inglis--- via tz wrote:
Nitpick:
As they are repeating 2024-02-29 23.00-24.00 so 2024-03-01 is delayed an hour in regions observing UTC+6, should this decree not be going into effect on 2024-02-29 rather than 2024-03-01, assuming the translation below is correct?
..but that's what they are doing: • use of UTC + 06 h stops just before UTC + 06 h reaches 2024-03-01T00 (at 2024-02-29-T18Z) • use of UTC + 05 h starts with the value 2024-02-29T23 of UTC + 05 h (which is taken at 2024-02-29-T18Z) Michael Deckers.
On Sat, 20 Jan 2024 at 03:38, brian.inglis--- via tz <tz@iana.org> wrote:
Good choice of effective date - chances of time zone errors compounding inevitable leap day errors, for those still not yet up to date ;^% on the contents of Pope Gregory XIII's papal bull from 1582!
I'll admit there were parts of me that really wanted to find some reason to write 2024 Feb 29 24:00. ;) But, to me, the text of the decree clearly referred to 2024 Mar 1 0:00 or, as your translation puts it, "on the night of February 29, 2024 to March 1, 2024 (at 00:00 hours)".
Nitpick:
As they are repeating 2024-02-29 23.00-24.00 so 2024-03-01 is delayed an hour in regions observing UTC+6, should this decree not be going into effect on 2024-02-29 rather than 2024-03-01
Most here would almost definitely have written this decree with effect from 24:00 on 29 February, to avoid confusion that any part of 1 March is entered before the 23:xx hour is repeated a second time. But the writers of this decree chose to say 00:00, even though that's technically on 1 March, possibly figuring that specifying "midnight between two dates" would be clearer to the public than saying "24:00" could be. Fortunately the two approaches are equivalent as far as tzdb is concerned, so we can choose to follow the text. -- Tim Parenti
On Fri, 19 Jan 2024 at 16:56, Paul Eggert <eggert@cs.ucla.edu> wrote:
and to update some related commentary and diagnostics.
Thanks; I had noticed the issue with the newly created regions as well. I was a bit more hung up, though, on the ISO 3166-2:KZ codes. https://www.iso.org/obp/ui/#iso:code:3166:KZ and https://en.wikipedia.org/wiki/ISO_3166-2:KZ seem to imply that they were all changed from alphabetic to numeric codes in November 2022. Since it seems they're still useful to us, I've updated them in the attached patch 0001.
As you can see, zonenow.tab needs care and feeding when these sorts of changes are made. The file will need further changes after the clocks change in Kazakhstan in March (as well as in Greenland later in March). This sort of thing is one reason I put off creating zonenow.tab for so long....
That, and it seems more than a bit fiddly and error-prone. Western Kazakhstan belongs in +05 with Asia/Tashkent, where it's been and will remain after the change, and not with Asia/Dhaka in +06 even though that's listed directly above Kazakhstan's eastern regions that are transitioning. Fixup attached as 0002. -- Tim Parenti
On 2024-01-20 08:31, Tim Parenti wrote:
I was a bit more hung up, though, on the ISO 3166-2:KZ codes. https://www.iso.org/obp/ui/#iso:code:3166:KZ and https://en.wikipedia.org/wiki/ISO_3166-2:KZ seem to imply that they were all changed from alphabetic to numeric codes in November 2022.
Oh, thanks, I had missed that. I vaguely thought that there were both numeric and alphabetic codes and as the list was already sorted by the alphabetic codes I preferred that. But if they're numeric now (ouch) we should go with numeric as in your patch.
That, and it seems more than a bit fiddly and error-prone. Western Kazakhstan belongs in +05 with Asia/Tashkent, where it's been and will remain after the change, and not with Asia/Dhaka in +06 even though that's listed directly above Kazakhstan's eastern regions that are transitioning. Fixup attached as 0002.
Thanks for catching that thinko. Yes, it's a bit fiddly. I did attempt to generate zonenow.tab automatically but couldn't come up with anything that worked at all well with tzselect. So I settled for fiddly, with "make check" catching obvious errors (though obviously it can't catch arbitrary commentary errors such as the commentary error you just fixed).
participants (5)
-
brian.inglis＠systematicsw.ab.ca -
Michael H Deckers -
Paul Eggert -
Tim Parenti -
Zhanbolat Raimbekov