tree dd18268df7f6f3b72d5733b31e1f6a9c57ab77cc
parent 682a230923933a7157a41b88c7804b6b7d2abdfa
author Frank Tang <ftang@chromium.org> 1565363515 -0700
committer Jungshik Shin <jshin@chromium.org> 1565392480 +0000

Update IANA timezone db to 2019b

According to the announcement at
https://mm.icann.org/pipermail/tz-announce/2019-July/000056.html

     Brazil no longer observes DST.
     Palestine's 2019 spring-forward transition was on 03-29, not 03-30.

The tz-related files are updated by running update_tz.sh and ICU
data files are rebuilt.

Either in JS console in Chrome or v8 should work like these:
d8> new Date(Date.UTC(2020, 0, 20, 9, 59)).toLocaleString("en", {timeZone: "America/Sao_Paulo", timeZoneName: "long"})
d8> new Date(Date.UTC(2020, 0, 20, 9, 59)).toLocaleString("en", {timeZone: "America/Cuiaba", timeZoneName: "long"})
d8> new Date(Date.UTC(2020, 0, 20, 9, 59)).toLocaleString("en", {timeZone: "America/Campo_Grande", timeZoneName: "long"})

EXPECT to see these dates are under Standard Time.
"1/20/2020, 6:59:00 AM Brasilia Standard Time"
"1/20/2020, 5:59:00 AM Amazon Standard Time"
"1/20/2020, 5:59:00 AM Amazon Standard Time"

BEFORE this CL we got them under Summer Time.
"1/20/2020, 7:59:00 AM Brasilia Summer Time"
"1/20/2020, 6:59:00 AM Amazon Summer Time"
"1/20/2020, 6:59:00 AM Amazon Summer Time"

Notice the change only apply to future date and summer in Brazil
is during the winter of USA.

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