8283350: (tz) Update Timezone Data to 2022a

[satoyoshiki]

Please review this PR.
The changes only include updates of the zone files that was provided by IANA.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8283350: (tz) Update Timezone Data to 2022a

Reviewers

• Sean Coffey (@coffeys - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/7914/head:pull/7914
$ git checkout pull/7914

Update a local copy of the PR:
$ git checkout pull/7914
$ git pull https://git.openjdk.java.net/jdk pull/7914/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 7914

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/7914.diff

[satoyoshiki]

@naotoj @coffeys

[bridgekeeper]

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

@satoyoshiki To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command.

Applicable Labels

• build
• client
• compiler
• core-libs
• hotspot
• hotspot-compiler
• hotspot-gc
• hotspot-jfr
• hotspot-runtime
• i18n
• ide-support
• javadoc
• jdk
• jmx
• kulla
• net
• nio
• security
• serviceability
• shenandoah

[openjdk]

@satoyoshiki 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:

8283350: (tz) Update Timezone Data to 2022a

Reviewed-by: coffeys

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

• 1a84d75: 8283594: Improve docs of ElementScanner classes
• 8a04464: 8282860: Write a regression test for JDK-4164779
• 6917c39: 8283493: Create an automated regression test for RFE 4231298
• 0ee65e1: 8283465: Character.UnicodeBlock.NUM_ENTITIES is out of date
• f9137cb: 8280896: java/nio/file/Files/probeContentType/Basic.java fails on Windows 11
• 0b11b57: 8283222: improve diagnosability of runtime/8176717/TestInheritFD.java timeouts
• 138460c: 8163327: Remove 3DES from the default enabled cipher suites list
• f017739: 8282241: Invalid generic signature for redefined classes
• 3e73a0b: 8283237: CallSite should be a sealed class
• a771600: 8283279: [Testbug] Improve TestGetSwapSpaceSize
• ... and 21 more: https://git.openjdk.java.net/jdk/compare/85628a871df3fdeec1b422d1c01c222abe45d0a8...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 (@coffeys) 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).

[naotoj]

Looks good. BTW, why this PR is still in draft mode?

[satoyoshiki]

Looks good. BTW, why this PR is still in draft mode?

If my understanding is correct, all interactions here are sent to the corresponding e-mail alias after the PR is set to non-draft. So, to avoid unnecessary interactions in the alias, I usually initiated the PFR from draft. Do you think the PR should be non-draft from beginning?

[satoyoshiki]

/integrate

[openjdk]

@satoyoshiki
Your change (at version 4f6d469) is now ready to be sponsored by a Committer.

[naotoj]

Initiating a PR in draft mode is fine, but reviews should be performed openly. You can control which mail alias reviews are sent.

[coffeys]

/sponsor

[openjdk]

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

• a35afe8: 8283519: Hsdis with capstone should annotate output
• e6f707a: 8283437: Refactor imageio classes javadoc to use @throws instead of @exception
• af18b11: 8283574: Use Klass::_id for type checks in the C++ code
• 5cf580e: 8283587: [BACKOUT] Invalid generic signature for redefined classes
• 2ef9767: 8270331: [TESTBUG] Error: Not a test or directory containing tests: java/awt/print/PrinterJob/InitToBlack.java
• a6740c0: 8283408: Fix a C2 crash when filling arrays with unsafe
• 1a84d75: 8283594: Improve docs of ElementScanner classes
• 8a04464: 8282860: Write a regression test for JDK-4164779
• 6917c39: 8283493: Create an automated regression test for RFE 4231298
• 0ee65e1: 8283465: Character.UnicodeBlock.NUM_ENTITIES is out of date
• ... and 27 more: https://git.openjdk.java.net/jdk/compare/85628a871df3fdeec1b422d1c01c222abe45d0a8...master

Your commit was automatically rebased without conflicts.

[openjdk]

@coffeys @satoyoshiki Pushed as commit b05d4cc.

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