-
CSR
-
Resolution: Approved
-
P3
-
None
-
behavioral
-
low
-
Although there is a slight chance applications see incompatible behavior for pre-1970 dates for those zones, it would be pretty rare because 1) it is for pre-1970 dates, 2) "EST"/"MST"/"HST" are obsolete zone ids.
-
Implementation
Summary
Updating the TZ Data Base to 2024b in update releases
Problem
TZdata2024 changes announced on 5th September 2024 includes changes to "EST", "MST", and "HST", i.e., changing those time zones from distinct time zones to links to other time zones. Problem here is, previously they are defined as fixed offset zones, e.g., "EST" is "-05:00" without any DST transitions. With 2024b, "EST" is now a link to "America/Panama." As in the above quote, "America/Panama" has not observed DST since 1970, but offset did change before (i.e., not equal to fixed "-05:00").
This change has Java 8+ specification implications in java.time.ZoneId.SHORT_IDS field, they are explictly defined as fixed zones. Solution for jdk24+ to modify the mappings in ZoneId class which requires modification of the spec.
For update releases, will not make the same ZoneId changes due to current specification. Mappings in ZoneId changes will be made at later in maintenance release for specific versions with the spec changes
Solution
Override the definitions in 2024b for "EST", "MST", and "HST" with fixed offset ones.
A release note is planned to highlight this issue
Specification
No specification changes for update releases
- csr of
-
JDK-8342297 (tz) Update Timezone Data to 2024b
- Resolved