<i18n dev> RFR: 8148446: (tz) Support tzdata2016a

Masayoshi Okutsu masayoshi.okutsu at oracle.com
Thu Feb 4 06:47:01 UTC 2016

Hi Ramanand,

I noticed that the zones in Yakutsk Time [1] seem to have their own 
names, such as "Khandyga Time" for Asia/Khandyga, and you seem to follow 
that convention for Asia/Chita. That causes some mismatch between the 
long names and abbreviations.

I dag out some past tzdata fixes to see how that happened. What I found 
out is that the 2013b fix [2] used "Yakutsk Time", but that the 2013c 
[3] fix used "Khandyga Time". 2013b went to JDK 7 updates and earlier 
ones and 2013c went to 8. JDK 9 inherits the 8 fix.

I prefer to restore the 2013b convention for Asia/Yakutsk, Asia/Chita, 
and Asia/Khandyga to have:

     {"Yakutsk Time", "YAKT",
      "Yakutsk Summer Time", "YAKST",
      "Yakutsk Time", "YAKT"}


[1] https://en.wikipedia.org/wiki/Yakutsk_Time
[2] http://hg.openjdk.java.net/jdk7u/jdk7u-dev/jdk/rev/b8009df64dc8
[3] http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/ae35fdbab949

On 2/2/2016 8:00 PM, Ramanand Patil wrote:
> HI all,
> Please review the latest TZDATA integration (tzdata2016a) to JDK9.
> Bug  - https://bugs.openjdk.java.net/browse/JDK-8148446
> Webrev - http://cr.openjdk.java.net/~rpatil/8148446/webrev.00/
> All the TimeZone related tests are passed after integration.
> Regards,
> Ramanand.

More information about the i18n-dev mailing list