tree 1487f4be9232262b8be579a63113f23f9adc7625
parent 69c72a6dfe1d1ef5677db03920518638f535591f
author Frank Tang <ftang@chromium.org> 1554493537 -0700
committer Jungshik Shin <jshin@chromium.org> 1554845068 +0000

Update IANA timezone database to 2019a

2019a was announced on March 26 2019.

https://mm.icann.org/pipermail/tz-announce/2019-March/000055.html

Palestine "springs forward" on 2019-03-30 instead of 2019-03-23.
Metlakatla "fell back" to rejoin Alaska Time on 2019-01-20 at 02:00.


Either in JS console in Chrome or v8 should work like these:
new Date(Date.UTC(2019, 0, 20, 9, 59)).toLocaleString("en", {timeZone: "America/Metlakatla", timeZoneName: "long"})
new Date(Date.UTC(2019, 0, 20, 10, 00)).toLocaleString("en", {timeZone: "America/Metlakatla", timeZoneName: "long"})
new Date(Date.UTC(2019, 2, 10, 10, 59)).toLocaleString("en", {timeZone: "America/Metlakatla", timeZoneName: "long"})
new Date(Date.UTC(2019, 2, 10, 11, 00)).toLocaleString("en", {timeZone: "America/Metlakatla", timeZoneName: "long"})

EXPECT to see the 2nd and 3rd dates are under Alaska Time.
"1/20/2019, 1:59:00 AM Pacific Standard Time"
"1/20/2019, 1:00:00 AM Alaska Standard Time"
"3/10/2019, 1:59:00 AM Alaska Standard Time"
"3/10/2019, 3:00:00 AM Alaska Daylight Time"

BEFORE this CL we got the 2nd and third date in Pacific Time.
"1/20/2019, 1:59:00 AM Pacific Standard Time"
"1/20/2019, 2:00:00 AM Pacific Standard Time"
"3/10/2019, 2:59:00 AM Pacific Standard Time"
"3/10/2019, 3:00:00 AM Alaska Daylight Time"

Bug: 473288
Test: See the above.
Change-Id: Id5add2356fb235f31ab17da2eef74adabb1a21fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/deps/icu/+/1555215
Reviewed-by: Jungshik Shin <jshin@chromium.org>