8297804: (tz) Update Timezone Data to 2022g

[gnu-andrew]

This is a mostly clean backport of the latest tzdata update.

This pull request contains a backport of commit ce896731 from the openjdk/jdk repository.

The commit being backported was authored by Andrew John Hughes on 7 Dec 2022 and was reviewed by Naoto Sato.

Changes from the {11,13,15,17,19}u and 20 versions:

• timezone.xml does not exist in 8u so the addition there is omitted
• In metaZones.xml, America_Mountain is used instead of Mexico_Pacific. This is consistent with PR27 on top of which this PR is based (America/Ciudad_Juarez splits from America/Ojinaga). 8u does not contain definitions for Mexico_Pacific.
• The tzdata updates are duplicated in jdk/test/sun/util/calendar/zi/tzdata, as currently required for 8u testing.

Tests in java/util/TimeZone, java/time/test, sun/util/calendar, sun/util/resources and sun/text/resources all pass. The rearguard changes are identical to those for vanguard, as verified against the rearguard data generated using make rearguard_tarballs in the tzdata2022g distribution.

Thanks!

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8297804: (tz) Update Timezone Data to 2022g

Reviewers

• Dmitry Cherepanov (@dimitryc - Reviewer) ⚠️ Review applies to ac90f9d7
• Severin Gehwolf (@jerboaa - Reviewer) ⚠️ Review applies to ac90f9d7

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u pull/28/head:pull/28
$ git checkout pull/28

Update a local copy of the PR:
$ git checkout pull/28
$ git pull https://git.openjdk.org/jdk8u pull/28/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28

View PR using the GUI difftool:
$ git pr show -t 28

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk8u/pull/28.diff

[bridgekeeper]

👋 Welcome back andrew! A progress list of the required criteria for merging this PR into pr/27 will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 01: Full (f53a65e5)
• 00: Full (ac90f9d7)

[dimitryc]

Looks good.

[gnu-andrew]

Thanks both. Flagged with jdk8u-critical-request.

[openjdk-notifier]

The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout JDK-8297804
git fetch https://git.openjdk.org/jdk8u master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

@gnu-andrew This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8297804: (tz) Update Timezone Data to 2022g

Reviewed-by: dcherepanov, sgehwolf

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@gnu-andrew Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

[gnu-andrew]

I see jdk8u-critical-yes.

/integrate

[gnu-andrew]

@gnu-andrew Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

Rebasing is the right thing to do here, as Git will replace the commit from the dependent PR with the one that's been pushed. No point doing unnecessary work merging them.

[openjdk]

Going to push as commit c961cb9.

[openjdk]

@gnu-andrew Pushed as commit c961cb9.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.