On Fri, 7 Aug 2026 15:04:41 GMT, Oumaiyma Intissar <[email protected]> wrote:
>> This updates the JDK time zone data from `tzdata2026b` to `tzdata2026c`. >> >> The main tzdata changes included here are: >> >> - Morocco moves back to permanent UTC on 2026-09-20, removing future >> projected Ramadan negative-DST rules. >> - Alberta moves to permanent UTC-06, modeled with the traditional `CST` >> abbreviation after the temporary CLDR workaround period. >> - British Columbia modeling/commentary is updated from the upstream 2026c >> data. >> - Leap second metadata is refreshed with the new expiration date. >> - Related `TimeZoneData` test data is regenerated for `tzdata2026c`. >> >> The tests were adjusted where previous expectations depended on old tzdata >> behavior or assumed tzdata abbreviations and localized CLDR names would >> always match: >> >> - `NegativeDSTTest.java` and `TestZoneRules.java` no longer expect Morocco >> negative-DST transitions after the 2026 move to permanent UTC. >> - `Bug6329116.java` allows the known CLDR localized short-name mismatch >> for Edmonton/Vancouver and their aliases. >> - `TestZoneTextPrinterParser.java` restricts daylight-name expectations to >> zones with explicit CLDR DST-offset metadata, avoiding a false `Mountain >> Daylight Time` expectation for `America/Yellowknife`. >> >> All changed tests, plus tier1, tier2, and tier3 validation, passed. >> >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Oumaiyma Intissar has updated the pull request incrementally with one > additional commit since the last revision: > > requested changes @OumaIntissar Your change (at version 71d1dbdbcbdb21afcad612a868b8bab2ffd6d204) is now ready to be sponsored by a Committer. ------------- PR Comment: https://git.openjdk.org/jdk/pull/32240#issuecomment-5221126664
