8322725: (tz) Update Timezone Data to 2023d

[lutkerd]

Clean backport of tzdata2023d

---

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
• JDK-8322725 needs maintainer approval

Issue

• JDK-8322725: (tz) Update Timezone Data to 2023d (Enhancement - P3 - Approved)

Reviewers

• Aleksey Shipilev (@shipilev - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2104/head:pull/2104
$ git checkout pull/2104

Update a local copy of the PR:
$ git checkout pull/2104
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2104/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2104

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2104.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back dlutker! 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

• 00: Full (479af7a6)

[lutkerd]

/clean was clean backport done via PR command.

[openjdk]

@lutkerd Only OpenJDK Committers can use the /clean command

[shipilev]

So this is apparently the automatic /backport, but it is not marked clean, because the paths are different. Bots seemed to have auto-detected the moves correctly, and then correctly implicitly asked for reviews. Good bots.

I checked the change against the mainline commit (openjdk/jdk@2a9c358) and previous commit to jdk17u-dev (openjdk/jdk17u@f8408c7), and I think this is a correct thing to do.

[openjdk]

⚠️ @lutkerd This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[lutkerd]

/approval request backport of tzdata2023d. Local tests pass

[openjdk]

@lutkerd
8322725: The approval request has been created successfully.

[openjdk]

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

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

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

8322725: (tz) Update Timezone Data to 2023d

Reviewed-by: shade

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 7 new commits pushed to the master branch:

• 002270c: 8323021: Shenandoah: Encountered reference count always attributed to first worker thread
• bfd23ae: 8322772: Clean up code after JDK-8322417
• 1f95796: 8321599: Data loss in AVX3 Base64 decoding
• 2470cac: 8316693: Simplify at-requires checkDockerSupport()
• f59ca35: 8303605: Memory leaks in Metaspace gtests
• f001819: 8322985: [BACKOUT] 8318562: Computational test more than 2x slower when AVX instructions are used
• dff69b7: 8278028: [test-library] Warnings cleanup of the test library

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this 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 (@shipilev) 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).

[lutkerd]

/integrate

[openjdk]

@lutkerd
Your change (at version 479af7a) is now ready to be sponsored by a Committer.

[shipilev]

/sponsor

[openjdk]

Going to push as commit 26b5597.
Since your change was applied there have been 7 commits pushed to the master branch:

• 002270c: 8323021: Shenandoah: Encountered reference count always attributed to first worker thread
• bfd23ae: 8322772: Clean up code after JDK-8322417
• 1f95796: 8321599: Data loss in AVX3 Base64 decoding
• 2470cac: 8316693: Simplify at-requires checkDockerSupport()
• f59ca35: 8303605: Memory leaks in Metaspace gtests
• f001819: 8322985: [BACKOUT] 8318562: Computational test more than 2x slower when AVX instructions are used
• dff69b7: 8278028: [test-library] Warnings cleanup of the test library

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev @lutkerd Pushed as commit 26b5597.

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