-
Bug
-
Resolution: Not an Issue
-
P4
-
None
-
8u241
-
x86_64
-
windows_10
A DESCRIPTION OF THE PROBLEM :
As stated in https://mm.icann.org/pipermail/tz-announce/2016-September/000041.html, the "Asia/Rangoon" time zone in tzdb-2016f was renamed to "Asia/Yangon" in tzdb-2016g. However, this change does not appear in the tzdata bundled with Java, including the tzdata2019c bundled with 8u241.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. `ZoneRulesProvider.getVersions("UTC").keySet();` contains "2019c" (or anything else greater than "2016f")
2. `DateTimeZone.forID("Asia/Rangoon");` does not fail
3. `DateTimeZone.forID("Asia/Yangon");` fails with "The datetime zone id 'Asia/Yangon' is not recognised"
FREQUENCY : always
As stated in https://mm.icann.org/pipermail/tz-announce/2016-September/000041.html, the "Asia/Rangoon" time zone in tzdb-2016f was renamed to "Asia/Yangon" in tzdb-2016g. However, this change does not appear in the tzdata bundled with Java, including the tzdata2019c bundled with 8u241.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. `ZoneRulesProvider.getVersions("UTC").keySet();` contains "2019c" (or anything else greater than "2016f")
2. `DateTimeZone.forID("Asia/Rangoon");` does not fail
3. `DateTimeZone.forID("Asia/Yangon");` fails with "The datetime zone id 'Asia/Yangon' is not recognised"
FREQUENCY : always