On Wed, 16 Oct 2024 19:59:44 GMT, Naoto Sato <na...@openjdk.org> wrote:
>> Removing the old compatibility behavior switch for JDK1.1. With the >> integration of tzdata2024b, definitions of those three (deprecated) IDs >> changed again, so maintaining the JDK11 compatibility got less useful. >> Removing the compatibility behavior makes the code and test simpler. A CSR >> for the behavior change is drafted too. > > Naoto Sato has updated the pull request incrementally with one additional > commit since the last revision: > > Refined it more BTW, can we go even further and remove "EST", "HST" and "MST" from `SHORT_IDS`? IIUC the basis for keeping those 3 specifically as part of `SHORT_IDS` was the conflicting 1.1 behavior. Now that the old mapping is removed, those 3 will always map to the TZDB data, which has them as valid links in _backwards_ instead of the previous fixed offset zones. Or is there some other reason to keep them at this point? I guess there is also no benefit to incentivize the usage of _any_ 3 letter zone ID. ------------- PR Comment: https://git.openjdk.org/jdk/pull/21545#issuecomment-2418110547
