More ability to generate disruptive data churn report (part3)
1. Identify disruptive data sets that can be reviewed by TCs for each release.
2. Provide an ability to TCs as a BRS work item to capture disruptive data changes prior to ICU integration.
Pulling out from the design doc what I’d expect that are included in this PR:
First day of week
First week of year
ISO Currency Code
This isn’t available until we generate v39 Charts, right? i.e. this file (cldr-staging/churn.tsv )will be updated when our BRS task for generating Charts is done, is that right?
I made but then closed it, as not needed, per today's Infrastructure meeting.
There was an interesting connection with
The remaining items in the design doc are either canceled, or on hold pending clarification, per today's Infrastructure meeting. So I’m setting this ticket to Reviewing.
Example chart with the currency change:
Subsequently I made a minimal implementation of "Changes of symbols or codes that are cross-locale in some way such as the unknown currency symbol change '???' -> '¤'." New function:
Running that, it returns true in these cases:
– plus maybe a dozen more. I’ll make another PR.