CLDR-18245 Generate cldr-json 47.0.0-ALPHA1 and ALPHA2 #81
Conversation
-Built with cldr tags/release-47-alpha1 -Built with cldr-staging tags/release-47-alpha1 (downloaded as cldr-staging-release-47-alpha1.tar.gz)
|
@srl295 how does this look? Should I do cldr-generate-zip.sh now? |
| @@ -35,17 +36,17 @@ Make sure your `cldr-json` directory is otherwise clean (`git status`) | |||
|
|
|||
| ### Updating the Repository | |||
|
|
|||
| 1. Run `git checkout -b ...` to create a new branch. | |||
| 1. Run `git checkout -b ...` to create a new branch. Typical practice is to create a new branch for a major version, such as `v44`, and only merge it back to `main` upon release. | |||
There was a problem hiding this comment.
These changes to UPDATING.md are very helpful! In the context of this PR, the history is confusing. Changes to UPDATING.md are actually from a different PR, already merged, #71
btangmu
changed the title
| "full": "HHmmsszzzz", | ||
| "long": "HHmmssz", | ||
| "medium": "HHmmss", | ||
| "short": "HHmm" |
There was a problem hiding this comment.
I'm a little surprised at how many changes there are from alpha1 to alpha2. These changes to en-GS appear to be from unicode-org/cldr#4320 last week.
|
@srl295 I'll wait for your go-ahead to do cldr-generate-zip.sh and tag a release for alpha2 |
Looks good - the zip is needed so icu4x can test before going to npm |
Here it is: https://github.com/unicode-org/cldr-json/releases/tag/47.0.0-ALPHA2 About npm: when do we publish on npm? alpha1, alpha2, ...? We haven't published alpha1 on npm |
-Built with cldr tags/release-47-alpha1 (or alpha2 for the 2nd commit, see further comments below)
-Built with cldr-staging tags/release-47-alpha1 (downloaded as cldr-staging-release-47-alpha1.tar.gz) (or alpha2 for 2nd commit)