-
Notifications
You must be signed in to change notification settings - Fork 63
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-18178 Generate cldr-json 46.1.0-BETA1 #78
base: main
Are you sure you want to change the base?
Conversation
-Built with cldr tags/release-46-1-beta1 (a3eef1eb57) -Built with cldr-staging tags/release-46-1-beta1 (downloaded as cldr-release-46-1-beta1.zip)
@srl295 This is targeting main; is that right? Also, these warnings were shown:
|
Main is right and warnings look expected. Shouldn't be files added or removed. |
1 similar comment
Main is right and warnings look expected. Shouldn't be files added or removed. |
@srl295 what's the protocol for merging a PR like this to cldr-json? I see that we make a release tag like https://github.com/unicode-org/cldr-json/releases/tag/46.1.0-BETA1 , and upload the zip (cldr-46.1.0-BETA1-json-full.zip) to it, without merging the PR. Is it now officially BETA1, or is it not definitely BETA1 until the zip has been checked? After the zip has been checked, do we merge this PR to main? |
I've only merged final to main. |
Beta 3 in #79 |
-Built with cldr tags/release-46-1-beta1 (a3eef1eb57)
-Built with cldr-staging tags/release-46-1-beta1 (downloaded as cldr-release-46-1-beta1.zip)