United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-8025255 : (tz) Support tzdata2013g

Details
Type:
Enhancement
Submit Date:
2013-09-23
Status:
Closed
Updated Date:
2014-01-06
Project Name:
JDK
Resolved Date:
2013-10-16
Component:
core-libs
OS:
generic
Sub-Component:
java.time
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
8
Fixed Versions:

Related Reports
Backport:
Backport:
Backport:
Backport:
Backport:
Backport:
Backport:
Duplicate:
Relates:
Relates:
Relates:
Relates:

Sub Tasks

Description
2013e TZdata:

The 2013e release of the tz code and data is available.  It reflects
the following changes circulated on the tz mailing list:

  Changes affecting near-future time stamps

    This year Fiji will start DST on October 27, not October 20.
    (Thanks to David Wheeler for the heads-up.)  For now, guess that
    Fiji will continue to spring forward the Sunday before the fourth
    Monday in October.

  Changes affecting current and future time zone abbreviations

    Use WIB/WITA/WIT rather than WIT/CIT/EIT for alphabetic Indonesian
    time zone abbreviations since 1932.  (Thanks to George Ziegler,
    Priyadi Iman Nurcahyo, Zakaria, Jason Grimes, Martin Pitt, and
    Benny Lin.)  This affects Asia/Dili, Asia/Jakarta, Asia/Jayapura,
    Asia/Makassar, and Asia/Pontianak.

    Use ART (UTC-3, standard time), rather than WARST (also UTC-3, but
    daylight saving time) for San Luis, Argentina since 2009.

  Changes affecting Godthab time stamps after 2037 if version mismatch

    Allow POSIX-like TZ strings where the transition time's hour can
    range from -167 through 167, instead of the POSIX-required 0
    through 24.  E.g., TZ='FJT-12FJST,M10.3.1/146,M1.3.4/75' for the
    new Fiji rules.  This is a more-compact way to represent
    far-future time stamps for America/Godthab, America/Santiago,
    Antarctica/Palmer, Asia/Gaza, Asia/Hebron, Asia/Jerusalem,
    Pacific/Easter, and Pacific/Fiji.  Other zones are unaffected by
    this change.  (Derived from a suggestion by Arthur David Olson.)

    Allow POSIX-like TZ strings where daylight saving time is in
    effect all year.  E.g., TZ='WART4WARST,J1/0,J365/25' for Western
    Argentina Summer Time all year.  This supports a more-compact way
    to represent the 2013d data for America/Argentina/San_Luis.
    Because of the change for San Luis noted above this change does not
    affect the current data.  (Thanks to Andrew Main (Zefram) for
    suggestions that improved this change.)

    Where these two TZ changes take effect, there is a minor extension
    to the tz file format in that it allows new values for the
    embedded TZ-format string, and the tz file format version number
    has therefore been increased from 2 to 3 as a precaution.
    Version-2-based client code should continue to work as before for
    all time stamps before 2038.  Existing version-2-based client code
    (tzcode, GNU/Linux, Solaris) has been tested on version-3-format
    files, and typically works in practice even for time stamps after
    2037; the only known exception is America/Godthab.

  Changes affecting time stamps before 1970

    Pacific/Johnston is now a link to Pacific/Honolulu.  This corrects
    some errors before 1947.

    Some zones have been turned into links, when they differ from
    existing zones only in older data that was likely invented or that
    differs only in LMT or transition from LMT.  These changes affect
    only time stamps before 1943.  The affected zones are:
    Africa/Juba, America/Anguilla, America/Aruba, America/Dominica,
    America/Grenada, America/Guadeloupe, America/Marigot,
    America/Montserrat, America/St_Barthelemy, America/St_Kitts,
    America/St_Lucia, America/St_Thomas, America/St_Vincent,
    America/Tortola, and Europe/Vaduz.  (Thanks to Alois Treindl for
    confirming that the old Europe/Vaduz zone was wrong and the new
    link is better for WWII-era times.)

    Change Kingston Mean Time from -5:07:12 to -5:07:11.  This affects
    America/Cayman, America/Jamaica and America/Grand_Turk time stamps
    from 1890 to 1912.

    Change the UT offset of Bern Mean Time from 0:29:44 to 0:29:46.
    This affects Europe/Zurich time stamps from 1853 to 1894.  (Thanks
    to Alois Treindl).

    Change the date of the circa-1850 Zurich transition from 1849-09-12
    to 1853-07-16, overriding Shanks with data from Messerli about
    postal and telegraph time in Switzerland.

  Changes affecting time zone abbreviations before 1970

    For Asia/Jakarta, use BMT (not JMT) for mean time from 1923 to 1932,
    as Jakarta was called Batavia back then.

  Changes affecting API

    The 'zic' command now outputs a dummy transition when far-future
    data can't be summarized using a TZ string, and uses a 402-year
    window rather than a 400-year window.  For the current data, this
    affects only the Asia/Tehran file.  It does not affect any of the
    time stamps that this file represents, so zdump outputs the same
    information as before.  (Thanks to Andrew Main (Zefram).)

    The 'date' command has a new '-r' option, which lets you specify
    the integer time to display, a la FreeBSD.

    The 'tzselect' command has two new options '-c' and '-n', which lets you
    select a zone based on latitude and longitude.

    The 'zic' command's '-v' option now warns about constructs that
    require the new version-3 binary file format.  (Thanks to Arthur
    David Olson for the suggestion.)

    Support for floating-point time_t has been removed.
    It was always dicey, and POSIX no longer requires it.
    (Thanks to Eric Blake for suggesting to the POSIX committee to
    remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
    Heninger, Arthur David Olson, and Alois Treindl, for reporting
    bugs and elucidating some of the corners of the old floating-point
    implementation.)

    The signatures of 'offtime', 'timeoff', and 'gtime' have been
    changed back to the old practice of using 'long' to represent UT
    offsets.  This had been inadvertently and mistakenly changed to
    'int_fast32_t'.  (Thanks to Christos Zoulos.)

    The code avoids undefined behavior on integer overflow in some
    more places, including gmtime, localtime, mktime and zdump.

  Changes affecting the zdump utility

    zdump now outputs "UT" when referring to Universal Time, not "UTC".
    "UTC" does not make sense for time stamps that predate the introduction
    of UTC, whereas "UT", a more-generic term, does.  (Thanks to Steve Allen
    for clarifying UT vs UTC.)

  Data changes affecting behavior of tzselect and similar programs

    Country code BQ is now called the more-common name "Caribbean Netherlands"
    rather than the more-official "Bonaire, St Eustatius & Saba".

    Remove from zone.tab the names America/Montreal, America/Shiprock,
    and Antarctica/South_Pole, as they are equivalent to existing
    same-country-code zones for post-1970 time stamps.  The data for
    these names are unchanged, so the names continue to work as before.

  Changes affecting code internals

    zic -c now runs way faster on 64-bit hosts when given large numbers.

    zic now uses vfprintf to avoid allocating and freeing some memory.

    tzselect now computes the list of continents from the data,
    rather than have it hard-coded.

    Minor changes pacify GCC 4.7.3 and GCC 4.8.1.

  Changes affecting the build procedure

    The 'leapseconds' file is now generated automatically from a
    new file 'leap-seconds.list', which is a copy of
    <ftp://time.nist.gov/pub/leap-seconds.list>.
    A new source file 'leapseconds.awk' implements this.
    The goal is simplification of the future maintenance of 'leapseconds'.

    When building the 'posix' or 'right' subdirectories, if the
    subdirectory would be a copy of the default subdirectory, it is
    now made a symbolic link if that is supported.  This saves about
    2 MB of file system space.

    The links America/Shiprock and Antarctica/South_Pole have been
    moved to the 'backward' file.  This affects only nondefault builds
    that omit 'backward'.

  Changes affecting version-control only

    .gitignore now ignores 'date'.

  Changes affecting documentation and commentary

    Changes to the 'tzfile' man page

      It now mentions that the binary file format may be extended in
      future versions by appending data.

      It now refers to the 'zdump' and 'zic' man pages.

    Changes to the 'zic' man page

      It lists conditions that elicit a warning with '-v'.

      It says that the behavior is unspecified when duplicate names
      are given, or if the source of one link is the target of another.

      Its examples are updated to match the latest data.

      The definition of white space has been clarified slightly.
      (Thanks to Michael Deckers.)

    Changes to the 'Theory' file

      There is a new section about the accuracy of the tz database,
      describing the many ways that errors can creep in, and
      explaining why so many of the pre-1970 time stamps are wrong or
      misleading (thanks to Steve Allen, Lester Caine, and Garrett
      Wollman for discussions that contributed to this).

      The 'Theory' file describes LMT better (this follows a
      suggestion by Guy Harris).

      It refers to the 2013 edition of POSIX rather than the 2004 edition.

      It's mentioned that excluding 'backward' should not affect the
      other data, and it suggests at least one zone.tab name per
      inhabited country (thanks to Stephen Colebourne).

      Some longstanding restrictions on names are documented, e.g.,
      'America/New_York' precludes 'America/New_York/Bronx'.

      It gives more reasons for the 1970 cutoff.

      It now mentions which time_t variants are supported, such as
      signed integer time_t.  (Thanks to Paul Goyette for reporting
      typos in an experimental version of this change.)

      (Thanks to Philip Newton for correcting typos in these changes.)

    Documentation and commentary is more careful to distinguish UT in
    general from UTC in particular.  (Thanks to Steve Allen.)

    Add a better source for the Zurich 1894 transition.
    (Thanks to Pierre-Yves Berger.)

    Update shapefile citations in tz-link.htm.  (Thanks to Guy Harris.)


Here are links to the release files:

  ftp://ftp.iana.org/tz/releases/tzcode2013e.tar.gz
  ftp://ftp.iana.org/tz/releases/tzdata2013e.tar.gz

2013f tzdata:
The 2013f release of the tz code and data is available.  It reflects
the following changes, which were either circulated on the tz mailing
list or are relatively minor administrative changes:

  Changes affecting near-future time stamps

    Tocantins will very likely not observe DST starting this spring.
    (Thanks to Steffen Thorsen.)

    Jordan will likely stay at UTC+3 indefinitely, and will not fall
    back this fall.

    Palestine will fall back at 00:00, not 01:00.  (Thanks to Steffen Thorsen.)

  Changes affecting API

    The types of the global variables 'timezone' and 'altzone' (if present)
    have been changed back to 'long'.  This is required for 'timezone'
    by POSIX, and for 'altzone' by common practice, e.g., Solaris 11.
    These variables were originally 'long' in the tz code, but were
    mistakenly changed to 'time_t' in 1987; nobody reported the
    incompatibility until now.  The difference matters on x32, where
    'long' is 32 bits and 'time_t' is 64.  (Thanks to Elliott Hughes.)

  Changes affecting the build procedure

    Avoid long strings in leapseconds.awk to work around a mawk bug.
    (Thanks to Cyril Baurand.)

  Changes affecting documentation and commentary

    New file 'NEWS' that contains release notes like this one.

    Paraguay's law does not specify DST transition time; 00:00 is customary.
    (Thanks to Waldemar Villamayor-Venialbo.)

    Minor capitalization fixes.

  Changes affecting version-control only

    The experimental github repository now contains annotated and
    signed tags for recent releases, e.g., '2013e' for Release 2013e.
    Releases are tagged starting with 2012e; earlier releases were
    done differently, and tags would either not have a simple name or
    not exactly match what was released.

    'make set-timestamps' is now simpler and a bit more portable.


Here are links to the release files:

  ftp://ftp.iana.org/tz/releases/tzcode2013f.tar.gz
  ftp://ftp.iana.org/tz/releases/tzdata2013f.tar.gz

The files are also available via HTTP as follows:

  http://www.iana.org/time-zones/repository/releases/tzcode2013f.tar.gz
  http://www.iana.org/time-zones/repository/releases/tzdata2013f.tar.gz


2013g tzdata:
The 2013g release of the tz code and data is available.  It reflects
the following changes, which were either circulated on the tz mailing
list or are relatively minor technical or administrative changes:

  Changes affecting current and near-future time stamps

    Morocco now observes DST from the last Sunday in March to the last
    Sunday in October, not April to September respectively.  (Thanks
    to Steffen Thorsen.)

  Changes affecting 'zic'

    'zic' now runs on platforms that lack both hard links and symlinks.
    (Thanks to Theo Veenker for reporting the problem, for MinGW.)
    Also, fix some bugs on platforms that lack hard links but have symlinks.

    'zic -v' again warns that Asia/Tehran has no POSIX environment variable
    to predict the far future, fixing a bug introduced in 2013e.

  Changes affecting the build procedure

    The 'leapseconds' file is again put into the tzdata tarball.
    Also, 'leapseconds.awk', so tzdata is self-contained.  (Thanks to
    Matt Burgess and Ian Abbott.)  The timestamps of these and other
    dependent files in tarballs are adjusted more consistently.

  Changes affecting documentation and commentary

    The README file is now part of the data tarball as well as the code.
    It now states that files are public domain unless otherwise specified.
    (Thanks to Andrew Main (Zefram) for asking for clarifications.)
    Its details about the 1989 release moved to a place of honor near
    the end of NEWS.


Here are links to the release files:

  ftp://ftp.iana.org/tz/releases/tzcode2013g.tar.gz
  ftp://ftp.iana.org/tz/releases/tzdata2013g.tar.gz

The files are also available via HTTP as follows:

  http://www.iana.org/time-zones/repository/releases/tzcode2013g.tar.gz
  http://www.iana.org/time-zones/repository/releases/tzdata2013g.tar.gz
                                    

Comments
SQE have completed the testing of TZUpdater 1.3.61 where both 2013g and 2013h are presented. 
http://st2.ru.oracle.com/StatusTool2/faces/queryresult2.jsp?matrix_id=1000027124

No new issues found. 
So, SQE ok to take the fix into CPU 14_01.

The only concern we need 2013h in the CPU as well. 
                                     
2013-11-01
TZdata inclusion.
                                     
2013-10-29
URL:   http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/60e3cdbe8cdf
User:  lana
Date:  2013-10-22 17:23:08 +0000

                                     
2013-10-22
URL:   http://hg.openjdk.java.net/jdk8/tl/jdk/rev/60e3cdbe8cdf
User:  coffeys
Date:  2013-10-16 20:22:14 +0000

                                     
2013-10-16
This change is more controversial than most in recent time-zone database history. The maintainer of tzdb has chosen an aggressive approach to "cleanup" which has resulted in deletion or change of data that was unnecessary.

The first example are changes in the Caribbean islands, where data indicating the start of time-zone history has been changed. Both the old and new values for the data are based on guesswork, however the new value is based on guesswork for a different location to the original.

The second example is McMurdo in Antarctica. This location was first inhabited in 1956. Previously, the tzdb data recognised this, and returned a fixed offset before that point. The 2013e data returns New Zealand data, resulting in the weird situation where an uninhabited location in Antarctica is defined as using DST.

The changes can be viewed here. https://github.com/jodastephen/tzdiff/commit/57aac13605f184a46f74d22f7dddc90e006c73aa

It is uncertain whether the tzdb data will continue to be aggressively "cleaned up" in this manner from this point forward. It may be worth considering whether Oracle needs to only select sensible changes from the tzdb data set, effectively forking the base data.

Mailing list archive - http://mm.icann.org/pipermail/tz/ - where I have been opposing the changes.
                                     
2013-09-23



Hardware and Software, Engineered to Work Together