Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLDR-18189 BRS 46.1 Update cldr & spec versions & status for final #4249

Conversation

pedberg-icu
Copy link
Contributor

@pedberg-icu pedberg-icu commented Dec 18, 2024

CLDR-18189

  • This PR completes the ticket.
  • Update readme to reflect correct version and status.
  • Remove -SNAPSHOT in pom.xml files
  • Update spec status

I generated production data after this and there were no updates, so the production data tagged beta3 is still the latest (and can presumably be tagged as final once the cldr maint/maint-46 branch is tagged as final).

ALLOW_MANY_COMMITS=true

@AEApple
Copy link
Contributor

AEApple commented Dec 18, 2024

Should Message format in the spec say it is 'Final Candidate'? Did I miss where it says that?

@srl295
Copy link
Member

srl295 commented Dec 18, 2024 via email

@AEApple
Copy link
Contributor

AEApple commented Dec 18, 2024

Well it isn't tech preview it is now 'Final candidate'. Is there standard wording we could use similar to what is done for tech preview to say that it is 'Final candidate'?

@srl295
Copy link
Member

srl295 commented Dec 18, 2024

@pedberg-icu I pushed table of contents updates to the PR that were missing (the ToC update tool needed to be run)

@pedberg-icu
Copy link
Contributor Author

@pedberg-icu I pushed table of contents updates to the PR that were missing (the ToC update tool needed to be run)

Ah, thanks! I had missed that.

@pedberg-icu
Copy link
Contributor Author

pedberg-icu commented Dec 18, 2024

As for the Message Format status, in regular 46 the Message Format spec says nothing about tech preview or final candidate so we should not add that in 46.1.

Copy link
Contributor

@AEApple AEApple left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, SGTM in that case

@pedberg-icu pedberg-icu merged commit a9b86e3 into unicode-org:maint/maint-46 Dec 18, 2024
9 checks passed
@pedberg-icu pedberg-icu deleted the CLDR-18189-BRS461-final-status-updates branch December 18, 2024 17:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants