-
Notifications
You must be signed in to change notification settings - Fork 384
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
CLDR-18189 BRS 46.1 Update cldr & spec versions & status for final #4249
Conversation
Should Message format in the spec say it is 'Final Candidate'? Did I miss where it says that? |
The only thing I see is that there are no references to tech preview in the document. If it said it was a tech preview before, it doesn’t now.
…--
Steven R. Loomis
Code Hive Tx, LLC
https://codehivetx.us
On Dec 18, 2024, at 10:59 AM, Annemarie Apple ***@***.***> wrote:
Should Message format in the spec say it is 'Final Candidate'? Did I miss where it says that?
—
Reply to this email directly, view it on GitHub <#4249 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGQZM5W4GJGYVR5T5PVDNL2GGSWDAVCNFSM6AAAAABTZXPTJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJRHAZTOMZQG4>.
You are receiving this because your review was requested.
|
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'? |
@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. |
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. |
There was a problem hiding this 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
CLDR-18189
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