tools: update tzdata to 2019c

[albertyw]

Based on the instructions in #30211 (comment), I updated the time zone database separately from the rest of the ICU data. This should be a cut-down version of #30232 .

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[Trott]

@srl295 @MylesBorins @nodejs/intl

[srl295]

LGTM

[MylesBorins]

I would like us to fastrack this

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/26528/

[srl295]

note also #29540

[Trott]

This needs one more approval before it can land. @MylesBorins ?

[srl295]

So this could be a periodic chore.

Related: I don't think we want to go down the route where npm install full-icu-tz becomes the new npm install full-icu do we?

[richardlau]

So this could be a periodic chore.

Related: I don't think we want to go down the route where npm install full-icu-tz becomes the new npm install full-icu do we?

That depends on how often timezone data changes and whether we want to enable a pathway where users can apply timezone fixes without having to update Node.js (thinking more of the LTS lines here where releases are more spread out, unless we need to class timezone updates as more urgent requiring out-of-schedule releases).

cc @nodejs/lts

[albertyw]

tzdata changes pretty often. For example, 2018 saw 9 tzdata updates. 2019 so far has had 3. For node to stay up to date, a diff like this should happen every few months. (it just so happens that most changes are relatively minor, like for Fiji or North Korea; the current push is because a much larger country Brazil decided to change its time zone policy).

Ref: https://data.iana.org/time-zones/tzdb/NEWS

[targos]

Rubber stamp

[targos]

Landed in 31ea341

[targos]

@MylesBorins @srl295 If we want to land it on v12.x, we need a backport PR because the data file is different there (not compressed, small-icu).