'Pyongyang Time' scrapped as North Korea synchronises clocks with the South
Hello, I am Sungwoo Kim, leave in Seoul, Republic of Korea. (South Korea) Since 5. 5. 2018, Pyongyang Time - North Korea time - had synchronized with South. We should discussion how we can synchronize PYT to KST with less side-effect. Here is articles include more information and backgrounds. https://www.telegraph.co.uk/news/2018/05/05/pyongyang-time-scrapped-north-ko... http://www.xinhuanet.com/english/2018-05/05/c_137158132.htm http://calgarysun.com/news/world/no-more-pyongyang-time-north-korea-changes-... https://qz.com/1265352/north-korea-will-reunifying-its-time-zone-with-south-...
Kim Sungwoo wrote:
We should discussion how we can synchronize PYT to KST with less side-effect. The current tzdb release (2018e) already has North Korea using the same time as South Korea, so tzdb is already synchronized reasonably well. Please see the announcement here:
https://mm.icann.org/pipermail/tz-announce/2018-May/000050.html Although there is a delay before this release's information hits everybody's cell phones and computers, it's not clear how the tz project itself could shorten that delay. Typically, most of the delay is downstream. If a government gives only a week's notice about a change, as North Korea did, the delay means that cell phones and computers will likely not be updated in time. For more about this and how governments can do better, please see: https://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/
Paul Eggert wrote:
The current tzdb release (2018e) already has North Korea using the same time as South Korea, so tzdb is already synchronized reasonably well.
Doesn't the 2018e release have the original update for Asia/Pyongyang (offset changed at 00:00 on 2018-05-05) but not the later correction (offset changed at 23:30 2018-05-04)? Looking at the 2018e tag on Paul's GitHub mirror [1], it contains the commit for the former [2] but not for the latter [3]. Was the release updated elsewhere? I'm new to the list and to tzdb in general. Just wanted to make sure I understand how everything works. Best, Scott [1] 2018e release tag on GitHub: https://github.com/eggert/tz/commits/2018e [2] Original update on GitHub: https://github.com/eggert/tz/commit/511df4d784a90340397d30966ccfd002bca2fdc1 [3] Corrected update on GitHub: https://github.com/eggert/tz/commit/e6c0e45e95605681d6280e6e6c606cf1d25ef409
On 9 May 2018 at 14:46, Scott Kilpatrick <Scott.Kilpatrick@twosigma.com> wrote:
Paul Eggert wrote:
The current tzdb release (2018e) already has North Korea using the same time as South Korea, so tzdb is already synchronized reasonably well.
Doesn't the 2018e release have the original update for Asia/Pyongyang (offset changed at 00:00 on 2018-05-05) but not the later correction (offset changed at 23:30 2018-05-04)?
That's correct, and is why Paul said tzdb is synchronized "reasonably well" and not "perfectly". Since the delta is in the past now, though, it's considered a change to past time stamps, which is not generally considered as urgent for cutting a new release. It will likely wait until we have more pressing/timely changes to make for the next version. -- Tim Parenti
participants (4)
-
Kim Sungwoo -
Paul Eggert -
Scott Kilpatrick -
Tim Parenti