8348328: Update IANA Language Subtag Registry to Version 2025-05-15

[RadekCap]

Backport of JDK-8348328 - Update IANA Language Subtag Registry to Version 2025-05-15

The IANA Functions Operator has updated the language subtag registry to "2025-05-15".

Clean backport.
Passed tier1 tests.

There are the same failures on the master branch in a local run:

compiler/escapeAnalysis/TestFindInstMemRecursion.java: 
test result: Failed. Execution failed: `main' threw exception: java.awt.AWTError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable.

serviceability/sa/ClhsdbPstack.java#core
test result: Error. Program `/home/rcap/git/github/jdk21u-dev/build/linux-x86_64-server-release/images/jdk/bin/java' timed out (timeout set to 1920000ms, elapsed time including timeout handling was 1920178ms).

serviceability/sa/ClhsdbPstack.java#process
test result: Error. Program `/home/rcap/git/github/jdk21u-dev/build/linux-x86_64-server-release/images/jdk/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 480217ms).

serviceability/sa/TestJhsdbJstackMixed.java:
test result: Error. "driver" action timed out with a timeout of 480 seconds on agent 58

java/foreign/nested/TestNested.java
test result: Failed. Compilation failed: Compilation failed

GH Actions are passing, Windows failures are unrelated.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8348328 needs maintainer approval

Issue

• JDK-8348328: Update IANA Language Subtag Registry to Version 2025-05-15 (Enhancement - P4 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1846

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8348328: Update IANA Language Subtag Registry to Version 2025-05-15

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

• 28276ac: 8355475: UNCTest should use an existing UNC path
• a7f1e32: 8350582: Correct the parsing of the ssl value in javax.net.debug
• 7e0f520: 8352719: Add an equals sign to the modules statement
• ... and 118 more: https://git.openjdk.org/jdk21u-dev/compare/27b6284bdd3ec7d627ccde9ddd22ea47e7463834...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.

➡️ 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).

[openjdk]

⚠️ @RadekCap the commit 9bcfa2f381bbc802b9d46721e5cbdeed2d90d86b does not refer to an issue in project JDK.

[openjdk]

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

[openjdk]

⚠️ @RadekCap 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.

[mlbridge]

Webrevs

• 00: Full (0e02b810)

[RadekCap]

/approval request Update IANA Language Subtag Registry to Version 2025-05-15

[openjdk]

@RadekCap
8348328: The approval request has been created successfully.

[RadekCap]

/approval request Update IANA Language Subtag Registry to Version 2025-05-15

[openjdk]

@RadekCap
8348328: The approval request was already up to date.

[GoeLin]

HI @RadekCap
if this gets approved for 24u, we want to get this into the July update.
Thus, in this case, we will need a PR agains jdk21u, not jdk21u-dev.
But we need to wait on the decision for 24u.
I remove the approval tag in the meantime. Please label again if it get's denied for 24u (or does not make the July update).
If it makes the July update of 24u, please open a PR agains jdk21u and label jdk21u-critical-request.

[RadekCap]

Hi @GoeLin,

Yes, I'm waiting for 24u approval. Let's see which will come sooner: the July update or 24u approval.
If approved first, I'll create a PR against 24u and close this one. The same situation will likely apply to 17 (PR already exists and waiting for 24u, 21u approval), and later to 11.

[gnu-andrew]

HI @RadekCap if this gets approved for 24u, we want to get this into the July update. Thus, in this case, we will need a PR agains jdk21u, not jdk21u-dev. But we need to wait on the decision for 24u. I remove the approval tag in the meantime. Please label again if it get's denied for 24u (or does not make the July update). If it makes the July update of 24u, please open a PR agains jdk21u and label jdk21u-critical-request.

I don't see anything going into 24u at this juncture. I can't see a closure message on the jdk-updates-dev mailing list, but apparently it entered RDP 2 as long ago as April 22nd, right after the last release. July's release will be the last update for 24u, before 25 is released in September.

If we do want to get this into July ourselves, we should do so ASAP as the freeze is imminent (a week today for 17u & 21u, the Friday for 11u)

Generally, I would say give the latest release two weeks and proceed with the LTS releases if nothing is approved in that time frame.

[gnu-andrew]

/approval request Update IANA Language Subtag Registry to Version 2025-05-15

Approval requests should really explain why this should be backported to the update, the expected risk and testing that has been done, so that the approver can make an informed decision.

[RadekCap]

Updating the approval request to make the review easier.

/approval request Update IANA Language Subtag Registry to Version 2025-05-15 Update to the latest IANA version. Clean backport. Passed tier1 tests. Passed gtests.

[openjdk]

@RadekCap
8348328: The approval request has been updated successfully.

[RadekCap]

Converting to draft as I'll use to add to the following CPU release.

[RadekCap]

@GoeLin Hi, please review 21u PR if you have time, so we can include it in the following CPU release:

openjdk/jdk21u#465

Thank you.

[RadekCap]

/approval request Update IANA Language Subtag Registry to Version 2025-05-15 Update to the latest IANA version. Clean backport. Passed tier1 tests. Passed gtests.

[openjdk]

@RadekCap
8348328: Approval has already been requested and approved.

[RadekCap]

/integrate

[openjdk]

@RadekCap
Your change (at version 0e02b81) is now ready to be sponsored by a Committer.

[phohensee]

/sponsor

[openjdk]

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

• b407af9: 8355249: Remove the use of WMIC from the entire source code
• 28276ac: 8355475: UNCTest should use an existing UNC path
• a7f1e32: 8350582: Correct the parsing of the ssl value in javax.net.debug
• ... and 119 more: https://git.openjdk.org/jdk21u-dev/compare/27b6284bdd3ec7d627ccde9ddd22ea47e7463834...master

Your commit was automatically rebased without conflicts.

[openjdk]

@phohensee @RadekCap Pushed as commit 06ff0d6.

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