8292579: (tz) Update Timezone Data to 2022c

[alvdavi]

Backport of tzdata 2022c to jdk8u using the rearguard data. This is the same change as openjdk/jdk8u-dev#119 but targeting jdk8u as suggested, aiming for this to be included as a critical fix for October release

---

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-8292579: (tz) Update Timezone Data to 2022c

Reviewers

• Andrew John Hughes (@gnu-andrew - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 19

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

Using diff file

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

[bridgekeeper]

👋 Welcome back alvdavi! A progress list of the required criteria for merging this PR into master 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 (dfba375e)
• 00: Full (6de9d963)

[gnu-andrew]

I've opened #20 to bring in the tests as we have on 17u. This patch will need to be updated to include the test update.

[gnu-andrew]

Can we get this one updated, as with 11u & 17u? Rampdown closes at the end of this week, at which point 8u is frozen for release.

[openjdk-notifier]

@alvdavi Please do not rebase or force-push to an active PR as it invalidates existing review comments. All changes will be squashed into a single commit automatically when integrating. See OpenJDK Developers’ Guide for more information.

[alvdavi]

I've updated this PR to account for the changes added in #20. I've ran the tests and they do pass.

The rest of the PR is unchanged, an import of rearguard data from 2022c.

Sorry about the force-push

[gnu-andrew]

Looks correct to me, clean backport bar the changes for rearguard and the additional copies of the tzdata files in 8u

Please label the bug with jdk8u-critical-request and I'll approve.

[openjdk]

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

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

8292579: (tz) Update Timezone Data to 2022c

Reviewed-by: andrew

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@gnu-andrew) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[alvdavi]

/integrate

[openjdk]

@alvdavi
Your change (at version dfba375) is now ready to be sponsored by a Committer.

[gnu-andrew]

Approved for 8u

[gnu-andrew]

/sponsor

[openjdk]

Going to push as commit 46da2c3.

[openjdk]

@gnu-andrew @alvdavi Pushed as commit 46da2c3.

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