-
Bug
-
Resolution: Fixed
-
P4
-
openjdk8u452, 11.0.27, 17.0.15, 21.0.7
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8352996 | 21.0.8 | Andrew Hughes | P4 | Resolved | Fixed | master |
JDK-8352998 | 17.0.16 | Andrew Hughes | P4 | Resolved | Fixed | master |
JDK-8352878 | 17.0.15 | Andrew Hughes | P4 | Resolved | Fixed | b05 |
JDK-8353268 | 11.0.28 | Andrew Hughes | P4 | Resolved | Fixed | master |
JDK-8352976 | 11.0.27 | Andrew Hughes | P4 | Resolved | Fixed | b05 |
JDK-8353114 | openjdk8u452 | Andrew Hughes | P4 | Resolved | Fixed | b07 |
While the 24u backport did update zone.tab, the 21u backport - and subsequent backports to 17u, 11u & 8u based on this - did not,due to being based on the trunk backport.
We should apply the zone.tab update to the 2025a updates in the upcoming April releases. Long-term, we should look at the possibility of backporting
- backported by
-
JDK-8352878 (tz) zone.tab update missed in 2025a backport
-
- Resolved
-
-
JDK-8352976 (tz) zone.tab update missed in 2025a backport
-
- Resolved
-
-
JDK-8352996 (tz) zone.tab update missed in 2025a backport
-
- Resolved
-
-
JDK-8352998 (tz) zone.tab update missed in 2025a backport
-
- Resolved
-
-
JDK-8353114 (tz) zone.tab update missed in 2025a backport
-
- Resolved
-
-
JDK-8353268 (tz) zone.tab update missed in 2025a backport
-
- Resolved
-
- caused by
-
JDK-8348843 (tz) Update Timezone Data to 2025a
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk8u/b10963f0
-
Commit(master) openjdk/jdk11u/13dab160
-
Commit(master) openjdk/jdk17u/305512cc
-
Commit(master) openjdk/jdk21u/4d3a3c0e
-
Review(master) openjdk/jdk8u/71
-
Review(master) openjdk/jdk11u/101
-
Review(master) openjdk/jdk17u/405
-
Review(master) openjdk/jdk21u/460