Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8224560

(tz) Upgrade time-zone data to tzdata2019a

    Details

    • Subcomponent:
    • Resolved In Build:
      b05
    • CPU:
      generic
    • OS:
      generic

      Backports

        Description

        [Tue Mar 26 05:50:25 UTC 2019]

        The 2019a 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:

           Briefly:
             Palestine "springs forward" on 2019-03-30 instead of 2019-03-23.
             Metlakatla "fell back" to rejoin Alaska Time on 2019-01-20 at 02:00.

           Changes to past and future timestamps

             Palestine will not start DST until 2019-03-30, instead of 2019-03-23 as
             previously predicted. Adjust our prediction by guessing that spring
             transitions will be between 24 and 30 March, which matches recent practice
             since 2016. (Thanks to Even Scharning and Tim Parenti.)

             Metlakatla ended its observance of Pacific standard time,
             rejoining Alaska Time, on 2019-01-20 at 02:00. (Thanks to Ryan
             Stanley and Tim Parenti.)

           Changes to past timestamps

             Israel observed DST in 1980 (08-02/09-13) and 1984 (05-05/08-25).
             (Thanks to Alois Treindl and Isaac Starkman.)

           Changes to time zone abbreviations

             Etc/UCT is now a backward-compatibility link to Etc/UTC, instead
             of being a separate zone that generates the abbreviation "UCT",
             which nowadays is typically a typo. (Problem reported by Isiah
             Meadows.)

           Changes to code

             zic now has an -r option to limit the time range of output data.
             For example, 'zic -r @1000000000' limits the output data to
             timestamps starting 1000000000 seconds after the Epoch.
             This helps shrink output size and can be useful for applications
             not needing the full timestamp history, such as TZDIST truncation;
             see Internet RFC 8536 section 5.1. (Inspired by a feature request
             from Christopher Wong, helped along by bug reports from Wong and
             from Tim Parenti.)

           Changes to documentation

             Mention Internet RFC 8536 (February 2019), which documents TZif.

             tz-link.html now cites tzdata-meta
             <https://tzdata-meta.timtimeonline.com/>.

        Here are links to the release files:

           https://www.iana.org/time-zones/repository/releases/tzcode2019a.tar.gz
           https://www.iana.org/time-zones/repository/releases/tzdata2019a.tar.gz
           https://www.iana.org/time-zones/repository/releases/tzdb-2019a.tar.lz

        Links are also available via plain HTTP, and via FTP from
        ftp://ftp.iana.org/tz/releases with the same basenames as above.


        PS. If your tzdata parser does not yet support negative DST offsets,
        this particular release's data entries are also available in a
        rearguard-format tarball and signature that does not contain such
        offsets. This is intended to be a temporary transition aid for these
        parsers. The URLs are:

        https://web.cs.ucla.edu/~eggert/tz/release/2019a/tzdata2019a-rearguard.tar.gz
        https://web.cs.ucla.edu/~eggert/tz/release/2019a/tzdata2019a-rearguard.tar.gz.asc

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rpatil Ramanand Patil (Inactive)
                  Reporter:
                  rpatil Ramanand Patil (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: