CLDR BRS
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Task# DNRTarget DateStatusOwnerUnclear descr.?CHPre ReqTask DescriptionBug/How-To LinksOther Links
2
A00Resolve Disputes/ErrorsRTom/StevenclearChange ST to Resolutionhttps://docs.google.com/document/d/1w2vXC6aQJZr481e-QRVZh47MzS7soRckmOSCbksgfsg/edit#heading=h.gr2eio7u3dtz
3
A01Resolve Disputes/Errors STRallclearDispute Resolution - 0 errors in ST - or until determined that all remaining errors are known/documented.
4
A01.2Rall; begin at Vetting startclearCopy into spreadsheet, distribute among TC. Take care of all flagged items.
5
A03Resolve Disputes/ErrorsRTom/StevenclearChange ST to read-only ; modify cldr-unittest/build.xml to use -z final_testing instead of -z build on the datacheck target (This will change the behavior of the automated build. )https://docs.google.com/document/d/1w2vXC6aQJZr481e-QRVZh47MzS7soRckmOSCbksgfsg/edit#heading=h.gr2eio7u3dtz
6
A03.5Resolve Disputes/ErrorsRTom/KristiclearSend email to cldr-core2 when ST moves to Read-only mode.
(Removed ICU as this milestone is not of interest to ICU)
7
A04Resolve Disputes/ErrorsRTom/StevenBADA03Download from ST into master (must be done after A03 to avoid losing data!!)owners to cleanup admin-OutputAllFiles.jsp
8
Move to new Sites
9
A04.2RSteven/TomUpdatedScale the production server down to D12 (This will be be change to D14 as part of an SBR item: S19 as needed for the next release).https://docs.google.com/document/d/1w2vXC6aQJZr481e-QRVZh47MzS7soRckmOSCbksgfsg/edit#heading=h.kpk0lc8x768lhttps://ms.portal.azure.com
10
A04.4Resolve Disputes/ErrorsRTom/MarkBADA04Run ConsoleCheckCLDR vs. trunk, distribute errors to be fixed; (with options: -e -z final_testing - work the error count down to 0Check on this to see if necessary
11
A04.6RMark/TomBADA04Run RemoveEmptyCLDR.java to remove bogus files in annotations, etc.Tom to check if done by A04.
12
A04.8DNRdoneMarkBADA04.6Regenerate charts (add churn to regular chart generation)Mark to flesh-out descriptionFALSE
13
A04.9Finish Final CandidateNRmoot?Peter/MarkMake sure Known Issues from previous release are being taken care of.http://cldr.unicode.org/index/downloads/cldr-37#TOC-Known-Issues
14
A05Resolve Disputes/ErrorsRAnnemarie/Kristi/PeterBADA04.81. Produce recommendations for which locales have enough data to move from seed to common or vice versa. Bring to committee to make decision, and implement.
2. After item above, generate list of possible new locales for ICU and distribute to <icu-core@lists.sourceforge.net>, for discussion/approval before ICU integration.
Pretty much everything that meets the criteria to be in common (#1) except for 2-3 legacy exceptions (that would probably not meet those citeria): cu, io, ...
recommend by email; look at coverage chart for candidates. Recently we have been using >95% of basic coverage and >70% (or 75%?) of core coveragehttps://unicode.org/repos/cldr-aux/charts/37/supplemental/locale_coverage.html
15
A05.1Resolve Disputes/ErrorsDNRdoneKristi/AnnemarieUpdatedA04.8Review delta charts for sanity/data issues, and add info to release note page or bring recommendations to TC:

1. Review in the TC meeting: https://unicode-org.github.io/cldr-staging/charts/38/delta/supplemental-data.html and https://unicode-org.github.io/cldr-staging/charts/38/delta/bcp47.html
2. Review a locale for anything looking odd, eg https://unicode-org.github.io/cldr-staging/charts/38/delta/fr.html
3. Review Churn chart (new from v38) and bring issues to the TC https://github.com/unicode-org/cldr-staging/blob/master/docs/charts/38/tsv/churn.tsv
https://docs.google.com/spreadsheets/d/1N_FdTc17hiFGduNjDPjLColb_0xRTdOYVdF7qUmgut4/edit#gid=0https://unicode.org/repos/cldr-aux/charts/37/supplemental/locale_coverage.html
16
A05.5Resolve Disputes/ErrorsNRdoneTom/MarkclearA04Run the necessary CLDRModify passes as outlined in link to right.
Should be rerun whenever we make significant data changes. (For LRS, abbreviate run as check).
http://cldr.unicode.org/development/cldr-big-red-switch/cldrmodify-passes
17
A05.7Resolve Disputes/ErrorsRMeike/MarkBADA05.5Analyze differences between en_GB and en_001 (main and annotations), determine which data needs to move up to en_001 and any necessary corrections. (note that Time and Date formats cannot be moved without TC policy review)Meike is writing up notes. Requires running java (currently). Add TSV generation to charts.

Filed: https://unicode-org.atlassian.net/browse/CLDR-14081 for TSV generation
https://docs.google.com/spreadsheets/d/1coDH7G7EImf3veoQeYUh0wInd8g90XCLe4xSNqU4WdM/edit#gid=0
18
A06.1Resolve Disputes/ErrorsRYoshito/PeterclearReview ICU to see if we need to update ICU4J libraries in CLDR, and if so, update.
(Only needed in coordination with ICU and need code updates)
http://cldr.unicode.org/development/updating-icu-jar
19
A06.5Resolve Disputes/ErrorsDNRdoneAllclearReminder! Everyone to look at tickets requiring any manual data changes (that affect ICU!!) that need to go in before we attempt to freeze the main data.query for items in vNN that are not done, and review and track
20
A06.7Resolve Disputes/ErrorsDNRdoneKristi / Steven?Commit checker run #1: (not alpha blocker)
Run Shane's checker tool and Check the report "Active Tickets with Code and No Reviewer On Trunk" Ideally everything should be in review except items with Component=BRS.
https://docs.google.com/document/d/1VWmFU1twrFmp2met1Sw1Dwc4601DGuo437avkku4SQ0/edithttps://gist.github.com/srl295/1e162778680d4a4b50ae802df1aa2d97
21
A06.8DNRdoneKristiclearJira tickets Reminder to Assignees: CLDR TCs first review/send reminders on open tickets for current milestonehttps://unicode-org.atlassian.net/issues/?filter=10074https://docs.google.com/document/d/1VWmFU1twrFmp2met1Sw1Dwc4601DGuo437avkku4SQ0/edit#
22
A07.1Resolve Disputes/ErrorsDNRdone (effectively)MarkclearSend out note to cldr-core2 and Markus(to forward to ICU) about data freeze (for all manual changes). Data needs to be stable for the production phases leading up to Alpha.
23
A07.4Resolve Disputes/ErrorsDNRdone Feb 17Peter / YoshitoReview ICU to see if we need to update ICU4J libraries in CLDR, and if so, update.
(Only needed in coordination with ICU and need code updates)
http://cldr.unicode.org/development/updating-icu-jar
24
A07.9Resolve Disputes/ErrorsDNRdone (generation showed only space difference)Mark/Stevenupdated/clearRun GenerateDTD.java to write out DTD files in canonical form. Overwrites in-repo. Diff and check in.
25
A09Resolve Disputes/ErrorsDNRmootSteven/MarkUpdate the plurals as per the link: https://sites.google.com/site/cldr/development/updating-codes/update-plurals
26
A09.1Incorporate UCDDNRmootMarkus/Peter/MarkUpdate for any new version of Unihan, running GenerateUnihanCollators.java.http://cldr.unicode.org/development/development-process/design-proposals/unihan-data
27
A10Finish Supplemental DataNRdoneSteven/MarkMake sure version number in DTDs and GEN_VERSION in CLDRFile is updated to the current version. Don't forget the DTDs in the keyboards directory as well. and unicodeVersion in the ldmlSupplemental.dtdSearch *.dtd for [<!ATTLIST version]
Check CLDRFile.GEN_VERSION
28
A11Finish Supplemental DataDNRdone (didn't do subdivisions, but not needed yet)Yoshito / Mark / Steven / TomUpdate Language/Script/Region Subtags (check for likelysubtags coming from exemplars)http://cldr.unicode.org/development/updating-codes/update-languagescriptregion-subtags
29
A11.15Finish Supplemental DataNRdoneSteven/MarkUpdatedMake sure that currencies are updated: see Updating Codeshttps://sites.google.com/site/cldr/development/updating-codes/update-currency-codeshttp://cldr.unicode.org/development/updating-codeshttps://github.com/unicode-org/cldr/pull/655
30
A11.3Finish Supplemental DataDNRmootMark/PeterAdd any necessary annotations and collation info for candidates for the next Unicode Version.https://github.com/unicode-org/cldr/pull/679https://sites.google.com/site/cldr/development/generate-emoji-paths
31
A12Finish Supplemental DataDNRmoot (no changes)Yoshito / Steven/MarkClear/updatedUpdate supplemental data language/country/population from the spreadsheet, and do ConvertLanguageData.https://sites.google.com/site/cldr/development/updating-codes/update-language-script-infohttps://github.com/unicode-org/cldr/pull/663
32
A14Finish Supplemental DataNRdoneSteven/MarkUnclear about metadataEnsure UN codes are up to date, and the EU is up to date.https://sites.google.com/site/cldr/development/updating-codes/updating-un-codeshttp://europa.eu/about-eu/countries/member-countries/index_en.htmhttps://github.com/unicode-org/cldr/pull/664
33
A15Finish Supplemental DataNRmootSteven/KristiclearIf there are any currency or region changes from (A14, A11, A11.15), send notice to cldr-core2 and cldr-users; record on release page. Look for possible Geopolitical issues.No relevant changes, nothing to do.
34
A16Finish Supplemental DataDNRdoneYoshitoUpdate the tzdata files and verify that bcp47 data is consistent with latest tzdata
(make sure we at least have a test that every bcp47 short timezone has a tzdata timezone & vice versa)
http://cldr.unicode.org/development/updating-codes/update-for-timezone-changesNew instruction needed - new ticket - http://unicode.org/cldr/trac/ticket/8904https://github.com/unicode-org/cldr/pull/670
35
A18Finish Supplemental DataNRmootSteven/MarkA12 A11Script Metadata (only for new Unicode), LikelySubtags. (LikelySubtags requires A12) [and A11?]https://sites.google.com/site/cldr/development/updating-codes/updating-script-metadatahttp://sites.google.com/site/cldr/development/updating-codes/likelysubtagshttps://unicode-org.atlassian.net/browse/CLDR-14118Skip Script Metadata because we aren't in Unicode 14 yet?
36
A18.5Finish Supplemental DataDNRdone, no changesSteven/MarkA11 A16Update attribute validity info
MUST come after updating LSTR codes, currency, timezone, etc.
https://sites.google.com/site/cldr/development/updating-codes/update-validity-xml
37
A19Finish Supplemental DataNRmootPeter/Markcould merge w/ A11.3• Update emoji collation (run EmojiOrder.java), emoji annotations based on ESC recommendations (changes in English)https://sites.google.com/site/cldr/development/generate-emoji-paths
38
A21Finish Final CandidateDNRdone, PR-1055 for CLDR-14513Steven/MarkA05.5?Generate all algorithimically generated locales (like sr_Latn, de_CH. and yo_BJ, and new ha_NE ). Remember to do all of (main, annotations, subdivisions).https://sites.google.com/site/cldr/development/generate-algorithmic-localeshttps://unicode-org.atlassian.net/browse/CLDR-14119
39
A22.5Finish Final CandidateDNRmootAndrewZ/Steven/Mark• Generate the derived annotations with GenerateDerivedAnnotations.java. (Tool may need updates if there are new characters or RGI.)https://github.com/unicode-org/cldr/pull/680
40
A23Finish Final CandidateDNRmootPeter/YoshitoVerify that all of the key-type values in bcp47 are in en.xml, except for an exceptions list.ticket to add test for English is #9774Changes for CLDR 34: https://unicode.org/cldr/trac/ticket/11414No new keys/types added in bcp47 data since CLDR 37.
41
A23.5Finish Final CandidateDNRdone Feb 17PeterUpdate CLDR version information and links in readme.html, update licenses? for candidate
42
A23.52Finish Supplemental DataDNRmootMarkOnly for new Unicode versions. Run Segmenter.java in the unicode tools to produce the file corresponding to the Unicode rules.
Compare to the segments/root.xml to make sure that they are ok, and make any necessary changes, retaining the special rules that CLDR has for keeping emoji together.
NOTE: Should come earlier to allow time for manual changes in ICU.
43
A23.54Finish Supplemental DataDNRmootPeter/CraigCorneliusManually sync changes to ICU segment rules.
Note that ICU removed its copy of the Japanese word-break tailoring, replacing it with dictionary-based break per ICU #9353; however we keep the Japanese word-break tailoring in CLDR since we don't have the dictionary break.
44
A24.4Finish Final CandidateNRdoneTom/ Steven/MarkAll previous stepsRun the necessary CLDRModify passes as outlined in link.
Should be rerun whenever we make significant data changes. (For LRS, abbreviate run as check).
http://cldr.unicode.org/development/cldr-big-red-switch/cldrmodify-passes
45
A24.5DNRdoneMarkRebuild the chartshttp://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
46
A24.6Finish Final CandidateDNRdonePeterReady for ICU integration(Peter)
47
A24.62DNRdone Feb 18-25PeterA24.6Do ICU integration and fix data bugs that result
48
A24.65Finish Final CandidateDNRdone Feb 25Peter/John/RickA24.62Tag as alpha release (this time release-39-alpha4).
Send out note to cldr-dev that alpha is tagged. (before we have a complete spec ready).
49
A24.7DNRdoneSteven, MarkClearRun CompareFilesBetweenReleases2.java
to identify files added or removed (trunk vs last-release). The relevant results should be summarized in the Release notes page.
https://gist.github.com/srl295/9ccf97f6ca2a8c0a01b12588c8e4bde5
50
A24.8DNRdonePeter/Mark/KristiGet minimal release page (eg http://cldr.unicode.org/index/downloads/cldr-33) ready for alpha. Should at least have overview section. Say on release page we are in alpha.http://cldr.unicode.org/index/downloads/cldr-38
51
A25.0Finish Supplemental DataNRmootMark/StevenRun GenerateLanguageContainment.java from wikipedia data to update LanguageGroup.xml
Make sure to review any changes (language moving from one line to another, or deletions)
http://cldr.unicode.org/development/updating-codes/updating-language-groupshttps://unicode-org.atlassian.net/browse/CLDR-14116
52
A25.2Finish Supplemental DataDNRmootMarkUpdate Subdivision Subtags. If done after alpha, rebuild validity.http://cldr.unicode.org/development/updating-codes/updating-subdivision-codes
53
A25.4Finish Supplemental DataDNRmootMarkUpdate attribute validity info for subdivisions; regenerate ChartSubdivisionNameshttps://sites.google.com/site/cldr/development/updating-codes/update-validity-xml
54
A25.6Finish Supplemental DataRmootMarkUpdate Subdivision Translations. Need to do A21 again afterwards just for these.http://cldr.unicode.org/development/updating-codes/updating-subdivision-translations
55
A25.65DNRdonePeterRun GenerateProductionData.java to generate production-style data in cldr-staging/production, run tests on that data, checkin to repoTHINK THIS ALSO SHOULD BE BEFORE ALPHA
56
A25.7DNRmootTomPush to Survey Tool Production at Alpha.
(also st2: see link at right, and put in the git hash to be pushed)
https://github.com/unicode-org/cldr/actions?query=workflow%3Aproduction
57
A25.8DNRdoneMarkRebuild the chartshttp://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
58
A26Finish Final CandidateDNRdonePeter/Mark/Rick(to go out next day) Public announcement of alpha - tagged as release-39-alpha4
Rick: Update "news" item to have an Alpha row.
Peter: Send notice in email to cldr-users, unicore, unicode, icu-announce.
Rick: Post also as blog announcement (using the summary text).
pre-alpha announcement tasks for pages: http://cldr.unicode.org/development/brs-post-items#A26
59
A26.1ValidateNRmootYoshitoOrganize import statements in Java source code (make sure to *not* format merging lines).
https://sites.google.com/site/cldr/development/eclipse-setup?pli=1#TOC-Clean-Up-Source-Code
https://unicode-org.atlassian.net/browse/CLDR-13721
60
A26.2Finish Final CandidateDNRdoneSteven/Peter > PeterCreate maint branch, and tag as alpha release with release-<major version>-alpha, e.g: release-18-alpha
61
A26.3Finish Final CandidateDNRdoneDoesn't block beta: Rick to get list (Rick gets candidates from ST, Peter gets candidates from JIRA/github); Peter to edit into web page* Get contributors for http://cldr.unicode.org/index/acknowledgments
* Get list of those who contributed through Survey tool, Jira bugs fixed, and Github pull-reqs for the release. See the How-to info.
* Send a message to those people who contributed at least one item, (see the http://cldr.unicode.org/development/cldr-big-red-switch).
* This is NOT a blocker for the release; we can update that page at any time.
http://cldr.unicode.org/development/brs-post-items#A26-1
http://cldr.unicode.org/development/cldr-big-red-switch
62
A26.4Finish Final CandidateDNRdonePeterIntegrate into ICU, fix issues.
63
A26.5Finish Final CandidateNRdoneMarkCompare the DTDs to find out spec documentation tasks for missing items. Also diff root and en to catch new values.Need to move D01-D03 should go before B01http://www.unicode.org/cldr/charts/dev/supplemental/dtd_deltas.html
64
A26.6Finish Final CandidateDNRdoneMarkReview the suppressions in unittest/TestLdml2ICU.java (testLdml2Icu.txt) to make sure that all new structure is being copied into ICU is working correctly. File bugs for any omissions. Do a logKnownIssues for any suppressions.
65
A26.65DNRdoneTom/Steven/MarkUpdate to latest version of guava and gson libs, if not done in SBRSnew way with mvn: https://unicode-org.atlassian.net/browse/CLDR-14580 https://search.maven.org/artifact/com.google.guava/guava/29.0-jre/bundle https://search.maven.org/artifact/com.google.code.gson/gson/2.8.6/jar
66
A26.65DNR2021-03-10donePeter to tagDATA BETA: Last point for tagging dev version for integration of beta into ICU for changes that would affect ICU library code
67
A26.662021-03-10donePeterChange the release page and cldr.org to say beta.
68
A26.672021-03-10doneRickSend message to Rick's announcement list:
"CLDR v39 beta has reached data freeze, so no further changes will be made to the cldr data except for showstoppers. For more details see [release page link] (http://cldr.unicode.org/index/downloads/cldr-39). The planned date for the LDML specification freeze is [DATE]. (March 24, 2021.
69
A26.68Finish Final CandidateDNRdoneSteven/Peter > PeterTag as beta release with release-<major version>-beta, e.g: release-18-beta
70
A27Finish Final CandidateDNRdoneKristiVerify that all X blockers/critical are done (Except BRS task tickets)Current version (v38) ALL-Filter 10094https://unicode-org.atlassian.net/issues/?filter=10054
71
A27.13DNRdoneKristiReadiness for Beta: All tickets other than spec, doc, BRS, and Charts are in Review or Done
72
A27.14.5PostNRin progressMissing components and tickets in reviewKristiClean up all open tickets for release version
(NOT showstopper for release)
1. All tickets must have a Component
2. All tickets Resolution=Fix must have a Reviewer
3. All status must be DONE for the current Fix version
4. Set Priority (When it's Done, bulk change to Medium)

Jira ticket handling for the Release: CLDR TCs take action on unhandled tickets (From the Jira/github process doc):
1. TC members are expected to review the tickets they reported and bring to triage for prioritization
2. Send out a warning email ahead of time to CLDR core with a date when the Fix in version will be removed.
3. Remove Fix in version for any tickets that are not handled in a release
[CLDR BRS 27.14 (v38)-Filter 10129https://docs.google.com/document/d/1VWmFU1twrFmp2met1Sw1Dwc4601DGuo437avkku4SQ0/edit#heading=h.6eubxgjrklef
73
A27.5DNRdoneKristiCommit checker run #2
1. Request Steven to run Shane's Commit checker tool
2. Final check on Jira tickets cleanliness using Shane's Commit checker Report. "Commits for Open Jira Issue". Update Jira tickets if no actions were taken by the owners.
https://docs.google.com/document/d/1VWmFU1twrFmp2met1Sw1Dwc4601DGuo437avkku4SQ0/edit#heading=h.1qdbcenf11drhttps://gist.github.com/srl295/1e162778680d4a4b50ae802df1aa2d97
74
A28Finish Final CandidateDNRdone, doc updatedSteven/PeterUpdate ICU4J libraries in CLDR again (after ICU4J feature / code freeze & CLDR integration into ICU)http://cldr.unicode.org/development/updating-icu-jar
75
A29Finish Final CandidateNRdoneMark/PeterMake sure Known Issues from previous release are taken care of.

Delete any items that are taken care of.
File a bug on any item that is not, and copy into current release page.
http://cldr.unicode.org/index/downloads/cldr-37#TOC-Known-Issues
76
A31.5DNRmootStevenPush to Survey Tool Production at Beta.
77
A32.3Finish Final CandidateDNRmootYoshitoVerify that every BCP47 -u and -t extension key is documented in TR35 (file tickets for missing ones).Check changes under bcp47 folder and see if all new keys have explanation in LDML. A new value (value part of key-value pair) usually does not require a corresponding explanation in LDML.

CLDR 38 - dictionary break exclusion identifier "dx" is new, and the LDML specification was updated to include this.
78
A32.5Finish Final CandidateNRdone Peter, 24th lateSteven/PeterPart of normal integration:
Test CLDR with ICU: Build ICU4C and ICU4J that uses the final candidate, verifying that the tests pass -- insofar as CLDR data is concerned
This means running both the LDML2ICUConverter tool and the ConvertTransforms tool.
79
A33.1DNRmootMarkRebuild the chartshttp://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
80
A33.15DNRdoneMarkCompose blog post for beta
81
A33.2Finish Final CandidateNR2021-03-25doneRick/PeterSPEC BETA: Once the spec is mostly done, send out note about beta. See above under Alpha for details. Fix download page, News on front page, Send note to Rick. Emphasize feedback on http://www.unicode.org/reports/tr35/proposed.html.
82
A33.7Finish Final CandidateDNRmootPeterSync deprecated items: spec, DTD. (now just a spec thing);
Mark's comment: should we instead maybe generate a list of deprecated items mechanically, and point to that list, instead of including in spec? Peter: That seems like a good idea, I will file a ticket
http://www.unicode.org/cldr/charts/dev/supplemental/dtd_deltas.html
83
A34.5Finish Final CandidateDNRdoneMarkRun GenerateDTD.java to write out DTD files in canonical form.
84
A34.7Finish Final CandidateNR2021-04-02doneMarkGet the new/changed items for the release page.http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
85
A34.8Finish Final CandidateNRmootMarkGenerate the graphs for inclusion in the release page (see link), and add to release items. Get the items added from delta_summary.tsv (generated by charts)http://cldr.unicode.org/development/showlocalecoverage
86
A35Finish Final CandidateNRdoneMark/Peter
(all review and edit) - in progress
Review bugs, significant Modification items from the spec, http://www.unicode.org/cldr/charts/30/delta/supplemental-data.html, DTD chart, and produce a good summary of the high points for the release page and press release. Check changes in dtds, bcp47 files, root and en locales, supplementalData.xml, etc.
Make sure to supply a detailed Migration section, and a good "selling points" summary!!
https://unicode-org.atlassian.net/issues/?jql=project%3DCLDR%20AND%20status%20in%20(Reviewing%2C%20Done)%20AND%20fixVersion%20in%20(36%2C%2036-optional)
87
B01DNR2021-04-02doneKristi/StevenCommit checker run #3 (final): Run Shane's checker tool (Steven), verify resultshttps://gist.github.com/srl295/1e162778680d4a4b50ae802df1aa2d97
88
B02ValidateNR2021-04-05mootMarkMake sure the charts are all built with the latest data, as per Generating Charts:http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
89
B03ValidateNRin progress, generated beta 2 target mid-apr for final. Updated the release note with a linkStevenCreate JSON data (can generate from cldr-staging), and tag with appropriate release taghttps://sites.google.com/site/cldr/development/updating-codes/updating-json-data
90
B08ValidateDNRmootMeike /Kherishma /FredrikSimple sanity check of the ST on SmokeTest to prevent failures in the release version; Open main Locale view; Open German; Look at Languages; Look at Currencies; Open Dashboard, Open Reports ->Zones. Send email to group.https://unicode-org.atlassian.net/browse/CLDR-13746 -> Can enter dupicate data as treated as a new value
https://unicode-org.atlassian.net/projects/CLDR/issues/CLDR-13747 -> Ideally there should be a limit for space limited formats
http://st.unicode.org/smoketest/v#/de/Languages_K_N/
91
B10DNR2021-04-14mootTomPush to Survey Tool Production at pre-release, for sanity check
92
D01Prepare final docsDNR2021-04-02doneRick[change as necessary] Do preliminary scan of the spec for broken links, and other problems. Distribute to others to review/fix.Copy the latest (repository) files for "tr35-NNN.html" to directory reports/tr35/tr35-NN/ for the intermediate revision, and then run validation and link checks in-situ on each of them.
93
2021-03-31doneMarkdown spec fixes applied
94
D07.2Prepare final docsNR2021-04-05doneMark/PeterPrepare the announcement text for Rick to send out.https://docs.google.com/document/d/1_o-mGZkUgt68KqOJVV4OOWDUUzuRjp5AgwoMIKnWQ0M/edit#heading=h.jbmfnmsf2wuz
95
D07.35Prepare final docsNR2021-04-05doneMarkMake sure the charts are all built with the *final* data, removing the "beta" tag, as per Generating Charts:
(NOT showstopper for release); then copy to /latest/ directory
http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
96
D07.37Prepare final docsNR2021-04-05mootMark / PeterFix the draft press-release page (also used for the notice).
http://sites.google.com/site/cldr/development/cldr-big-red-switch/draft-press
In particular:
update the most recent boilerplate About Unicode from Ellen
replace the body by a summary of the release note, eg http://cldr.unicode.org/index/downloads/cldr-31
Fix the dates and versions throughout (don't forget the page title)
This step depends on D05-D07 above.
For a dot-dot release, take draft rel note draft from a recent dot-dot release, e.g. 1.7.2; for a dot release, use one of those, e.g. 1.8.
97
D07.38Prepare final docsDNR2021-04-05doneRickRemove the yellow from UTS#35 draft, and clean up everything for posting.
THIS HAS TO BE FINAL! All links in spec.
http://cldr.unicode.org/development/brs-post-items#D10
98
D07.4Prepare final docsNR2021-04-07doneRick/FredrikCheck all the links on the release page (link is example)http://cldr.unicode.org/index/downloads/cldr-39
99
D08Prepare final docsNR2021-04-07doneSteven, Rick[Rick, Steven: Figure out how to revise this for Markdown.]
• fix https://unicode-org.github.io/cldr-staging/
• all the above pages in step D7:
• all links work in spec, and release page links to spec.
all versions, tags, and dates are right
For at least a sample page in each section / subsection, verify with W3C tool that HTML is valid.
plus: http://www.unicode.org/draft/reports/tr35/tr35.html
Post the final spec under reports/tr35/[version]
After markdown is completed and convertd to HTML, posting the final spec involves putting the seven converted tr35*.html files into reports/tr35/tr35-NN/ directory for the correct latest revision, and then also copying those HTML files into reports/tr35/ main directory so that the "latest" version is at https://www.unicode.org/reports/tr35/ and the index.html file is a copy of tr35.html. This part has changed significantly now that the spec is in markdown.https://github.com/unicode-org/cldr/pull/1190
100
E01PostDNR2021-04-06donePeterUpdate CLDR version information and links in readme.html for final release