On 2026-10-21 13:46, Robert Bastian via tz wrote:
78.3 is the latest ICU release (79 releases on Thursday), but ICU provides
data packages for TZ data that are backwards compatible back to ICU 44:
https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew. This way
even old systems that cannot update ICU can receive updated time zone data.
Things should start getting more fun after Thursday, I suppose. (Hey, that's tomorrow!)

I'm a bit fuzzy about the relationship between CLDR version numbers, ICU version numbers, and CLDR patch numbers (and perhaps there are ICU patch numbers as well). Although Tim writes that there is a CLDR 48.2.3 that corresponds to tzdata 2026e, I didn't know about that CLDR patch number. And this leads me to wonder whether the following comments in TZDB's NEWS and northamerica files have the correct version numbers in them.

* TZDB's NEWS file says for 2026b, which updated data for BC, "works around a limitation in CLDR 48.1 (2026-01-08)." Is that "48.1" the last CLDR version that was incompatible with 2026b sans its temporary hack, or is there some later patch version of CLDR that was also incompatible with 2026b sans its temporary hack? (The "temporary hack" delays the effective date of the timekeeping rule change to November 1.)

* TZDB's northamerica file says that 2026c, which updated data for Alberta, "The temporary hack for Alberta is needed for CLDR 48.2 (2026-03-17) and earlier". Is that "48.2" the last CLDR version that was incompatible with 2026c sans its temporary hack, or is there some later patch version of CLDR that was also incompatible with 2026b sans its temporary hack?

If it's not easy to answer these questions that's OK, we can leave the commentary as-is, or (perhaps better) remove the possibly-not-quite-correct CLDR version numbers in the commentary.

Reply via email to