8322725: (tz) Update Timezone Data to 2023d

[lutkerd]

Update to the latest tzdata 2023d.

Similar fix to 11/17, but not a clean backport as 8 uses different format.
Tested: jdk/test/java/util/TimeZone jdk/test/java/time/test jdk/test/sun/util/resources jdk/test/sun/text/resources jdk/test/sun/util/calendar and all are passing.

---

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

• Severin Gehwolf (@jerboaa - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 414

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/414.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

• 01: Full - Incremental (4718bb60)
• 00: Full (48725abc)

[openjdk]

@lutkerd 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.

[shipilev]

We probably want @gnu-andrew to look through it.

[bridgekeeper]

@lutkerd This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[jerboaa]

LGTM.

[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 Low risk and local tests passing.

[openjdk]

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

[openjdk]

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

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

8322725: (tz) Update Timezone Data to 2023d

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

• 474c8c1: 8192931: Regression test java/awt/font/TextLayout/CombiningPerf.java fails
• 4a69ad2: 8324184: Windows VS2010 build failed with "error C2275: 'int64_t'"
• 552c686: Merge
• d4b472f: 8317547: Enhance TLS connection support
• 7c693ce: 8316976: Improve signature handling
• 199cb32: 8314468: Improve Compiler loops
• f7cb28d: 8314307: Improve loop handling
• 77d38b7: 8314295: Enhance verification of verifier
• 5e0e2bf: 8314284: Enhance Nashorn performance
• 7f5db81: 8308204: Enhanced certificate processing
• ... and 2 more: https://git.openjdk.org/jdk8u-dev/compare/d898d4018e0a16f2115f4b1cbf93eb5e653b789b...master

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 (@jerboaa) 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 4718bb6) is now ready to be sponsored by a Committer.

[jerboaa]

/sponsor

[openjdk]

Going to push as commit 15e2c0b.
Since your change was applied there have been 12 commits pushed to the master branch:

• 474c8c1: 8192931: Regression test java/awt/font/TextLayout/CombiningPerf.java fails
• 4a69ad2: 8324184: Windows VS2010 build failed with "error C2275: 'int64_t'"
• 552c686: Merge
• d4b472f: 8317547: Enhance TLS connection support
• 7c693ce: 8316976: Improve signature handling
• 199cb32: 8314468: Improve Compiler loops
• f7cb28d: 8314307: Improve loop handling
• 77d38b7: 8314295: Enhance verification of verifier
• 5e0e2bf: 8314284: Enhance Nashorn performance
• 7f5db81: 8308204: Enhanced certificate processing
• ... and 2 more: https://git.openjdk.org/jdk8u-dev/compare/d898d4018e0a16f2115f4b1cbf93eb5e653b789b...master

Your commit was automatically rebased without conflicts.

[openjdk]

@jerboaa @lutkerd Pushed as commit 15e2c0b.

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

[gnu-andrew]

Any idea why this backport lost the change to aliases.txt? I don't see any mention of this in the review. We have fixed this as part of openjdk/jdk8u#69