|Task#||DNR||Target Date||Status||Owner||Unclear descr.?||CH||Pre Req||Task Description||Bug/How-To Links||Other Links|
|A00||Resolve Disputes/Errors||R||Tom/Steven||clear||Change ST to Resolution||https://docs.google.com/document/d/1w2vXC6aQJZr481e-QRVZh47MzS7soRckmOSCbksgfsg/edit#heading=h.gr2eio7u3dtz|
|A01||Resolve Disputes/Errors ST||R||all||clear||Dispute Resolution - 0 errors in ST - or until determined that all remaining errors are known/documented.|
|A01.2||R||all; begin at Vetting start||clear||Copy into spreadsheet, distribute among TC. Take care of all flagged items.|
|A03||Resolve Disputes/Errors||R||Tom/Steven||clear||Change 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|
|A03.5||Resolve Disputes/Errors||R||Tom/Kristi||clear||Send email to cldr-core2 when ST moves to Read-only mode.|
(Removed ICU as this milestone is not of interest to ICU)
|A04||Resolve Disputes/Errors||R||Tom/Steven||BAD||A03||Download from ST into master (must be done after A03 to avoid losing data!!)||owners to cleanup||admin-OutputAllFiles.jsp|
|Move to new Sites|
|A04.2||R||Steven/Tom||Updated||Scale 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.kpk0lc8x768l||https://ms.portal.azure.com|
|A04.4||Resolve Disputes/Errors||R||Tom/Mark||BAD||A04||Run ConsoleCheckCLDR vs. trunk, distribute errors to be fixed; (with options: -e -z final_testing - work the error count down to 0||Check on this to see if necessary|
|A04.6||R||Mark/Tom||BAD||A04||Run RemoveEmptyCLDR.java to remove bogus files in annotations, etc.||Tom to check if done by A04.|
|A04.8||DNR||done||Mark||BAD||A04.6||Regenerate charts (add churn to regular chart generation)||Mark to flesh-out description||FALSE|
|A04.9||Finish Final Candidate||NR||moot?||Peter/Mark||Make sure Known Issues from previous release are being taken care of.||http://cldr.unicode.org/index/downloads/cldr-37#TOC-Known-Issues|
|A05||Resolve Disputes/Errors||R||Annemarie/Kristi/Peter||BAD||A04.8||1. 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 <firstname.lastname@example.org>, 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 coverage||https://unicode.org/repos/cldr-aux/charts/37/supplemental/locale_coverage.html|
|A05.1||Resolve Disputes/Errors||DNR||done||Kristi/Annemarie||Updated||A04.8||Review 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
|A05.5||Resolve Disputes/Errors||NR||done||Tom/Mark||clear||A04||Run 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).
|A05.7||Resolve Disputes/Errors||R||Meike/Mark||BAD||A05.5||Analyze 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
|A06.1||Resolve Disputes/Errors||R||Yoshito/Peter||clear||Review 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)
|A06.5||Resolve Disputes/Errors||DNR||done||All||clear||Reminder! 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|
|A06.7||Resolve Disputes/Errors||DNR||done||Kristi / 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.
|A06.8||DNR||done||Kristi||clear||Jira tickets Reminder to Assignees: CLDR TCs first review/send reminders on open tickets for current milestone||https://unicode-org.atlassian.net/issues/?filter=10074||https://docs.google.com/document/d/1VWmFU1twrFmp2met1Sw1Dwc4601DGuo437avkku4SQ0/edit#|
|A07.1||Resolve Disputes/Errors||DNR||done (effectively)||Mark||clear||Send 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.|
|A07.4||Resolve Disputes/Errors||DNR||done Feb 17||Peter / Yoshito||Review 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)
|A07.9||Resolve Disputes/Errors||DNR||done (generation showed only space difference)||Mark/Steven||updated/clear||Run GenerateDTD.java to write out DTD files in canonical form. Overwrites in-repo. Diff and check in.|
|A09||Resolve Disputes/Errors||DNR||moot||Steven/Mark||Update the plurals as per the link:||https://sites.google.com/site/cldr/development/updating-codes/update-plurals|
|A09.1||Incorporate UCD||DNR||moot||Markus/Peter/Mark||Update for any new version of Unihan, running GenerateUnihanCollators.java.||http://cldr.unicode.org/development/development-process/design-proposals/unihan-data|
|A10||Finish Supplemental Data||NR||done||Steven/Mark||Make 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.dtd||Search *.dtd for [<!ATTLIST version]|
|A11||Finish Supplemental Data||DNR||done (didn't do subdivisions, but not needed yet)||Yoshito / Mark / Steven / Tom||Update Language/Script/Region Subtags (check for likelysubtags coming from exemplars)||http://cldr.unicode.org/development/updating-codes/update-languagescriptregion-subtags|
|A11.15||Finish Supplemental Data||NR||done||Steven/Mark||Updated||Make sure that currencies are updated: see Updating Codes||https://sites.google.com/site/cldr/development/updating-codes/update-currency-codes||http://cldr.unicode.org/development/updating-codes||https://github.com/unicode-org/cldr/pull/655|
|A11.3||Finish Supplemental Data||DNR||moot||Mark/Peter||Add any necessary annotations and collation info for candidates for the next Unicode Version.||https://github.com/unicode-org/cldr/pull/679||https://sites.google.com/site/cldr/development/generate-emoji-paths|
|A12||Finish Supplemental Data||DNR||moot (no changes)||Yoshito / Steven/Mark||Clear/updated||Update supplemental data language/country/population from the spreadsheet, and do ConvertLanguageData.||https://sites.google.com/site/cldr/development/updating-codes/update-language-script-info||https://github.com/unicode-org/cldr/pull/663|
|A14||Finish Supplemental Data||NR||done||Steven/Mark||Unclear about metadata||Ensure UN codes are up to date, and the EU is up to date.||https://sites.google.com/site/cldr/development/updating-codes/updating-un-codes||http://europa.eu/about-eu/countries/member-countries/index_en.htm||https://github.com/unicode-org/cldr/pull/664|
|A15||Finish Supplemental Data||NR||moot||Steven/Kristi||clear||If 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.|
|A16||Finish Supplemental Data||DNR||done||Yoshito||Update 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-changes||New instruction needed - new ticket - http://unicode.org/cldr/trac/ticket/8904||https://github.com/unicode-org/cldr/pull/670|
|A18||Finish Supplemental Data||NR||moot||Steven/Mark||A12 A11||Script Metadata (only for new Unicode), LikelySubtags. (LikelySubtags requires A12) [and A11?]||https://sites.google.com/site/cldr/development/updating-codes/updating-script-metadata||http://sites.google.com/site/cldr/development/updating-codes/likelysubtags||https://unicode-org.atlassian.net/browse/CLDR-14118||Skip Script Metadata because we aren't in Unicode 14 yet?|
|A18.5||Finish Supplemental Data||DNR||done, no changes||Steven/Mark||A11 A16||Update attribute validity info|
MUST come after updating LSTR codes, currency, timezone, etc.
|A19||Finish Supplemental Data||NR||moot||Peter/Mark||could 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|
|A21||Finish Final Candidate||DNR||done, PR-1055 for CLDR-14513||Steven/Mark||A05.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-locales||https://unicode-org.atlassian.net/browse/CLDR-14119|
|A22.5||Finish Final Candidate||DNR||moot||AndrewZ/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|
|A23||Finish Final Candidate||DNR||moot||Peter/Yoshito||Verify 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 #9774||Changes for CLDR 34: https://unicode.org/cldr/trac/ticket/11414||No new keys/types added in bcp47 data since CLDR 37.|
|A23.5||Finish Final Candidate||DNR||done Feb 17||Peter||Update CLDR version information and links in readme.html, update licenses? for candidate|
|A23.52||Finish Supplemental Data||DNR||moot||Mark||Only 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.|
|A23.54||Finish Supplemental Data||DNR||moot||Peter/CraigCornelius||Manually 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.
|A24.4||Finish Final Candidate||NR||done||Tom/ Steven/Mark||All previous steps||Run the necessary CLDRModify passes as outlined in link.|
Should be rerun whenever we make significant data changes. (For LRS, abbreviate run as check).
|A24.5||DNR||done||Mark||Rebuild the charts||http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts|
|A24.6||Finish Final Candidate||DNR||done||Peter||Ready for ICU integration(Peter)|
|A24.62||DNR||done Feb 18-25||Peter||A24.6||Do ICU integration and fix data bugs that result|
|A24.65||Finish Final Candidate||DNR||done Feb 25||Peter/John/Rick||A24.62||Tag 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).
|A24.7||DNR||done||Steven, Mark||Clear||Run CompareFilesBetweenReleases2.java|
to identify files added or removed (trunk vs last-release). The relevant results should be summarized in the Release notes page.
|A24.8||DNR||done||Peter/Mark/Kristi||Get 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|
|A25.0||Finish Supplemental Data||NR||moot||Mark/Steven||Run GenerateLanguageContainment.java from wikipedia data to update LanguageGroup.xml|
Make sure to review any changes (language moving from one line to another, or deletions)
|A25.2||Finish Supplemental Data||DNR||moot||Mark||Update Subdivision Subtags. If done after alpha, rebuild validity.||http://cldr.unicode.org/development/updating-codes/updating-subdivision-codes|
|A25.4||Finish Supplemental Data||DNR||moot||Mark||Update attribute validity info for subdivisions; regenerate ChartSubdivisionNames||https://sites.google.com/site/cldr/development/updating-codes/update-validity-xml|
|A25.6||Finish Supplemental Data||R||moot||Mark||Update Subdivision Translations. Need to do A21 again afterwards just for these.||http://cldr.unicode.org/development/updating-codes/updating-subdivision-translations|
|A25.65||DNR||done||Peter||Run GenerateProductionData.java to generate production-style data in cldr-staging/production, run tests on that data, checkin to repo||THINK THIS ALSO SHOULD BE BEFORE ALPHA|
|A25.7||DNR||moot||Tom||Push to Survey Tool Production at Alpha.|
(also st2: see link at right, and put in the git hash to be pushed)
|A25.8||DNR||done||Mark||Rebuild the charts||http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts|
|A26||Finish Final Candidate||DNR||done||Peter/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|
|A26.1||Validate||NR||moot||Yoshito||Organize import statements in Java source code (make sure to *not* format merging lines).|
|A26.2||Finish Final Candidate||DNR||done||Steven/Peter > Peter||Create maint branch, and tag as alpha release with release-<major version>-alpha, e.g: release-18-alpha|
|A26.3||Finish Final Candidate||DNR||done||Doesn'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.
|A26.4||Finish Final Candidate||DNR||done||Peter||Integrate into ICU, fix issues.|
|A26.5||Finish Final Candidate||NR||done||Mark||Compare 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 B01||http://www.unicode.org/cldr/charts/dev/supplemental/dtd_deltas.html|
|A26.6||Finish Final Candidate||DNR||done||Mark||Review 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.|
|A26.65||DNR||done||Tom/Steven/Mark||Update to latest version of guava and gson libs, if not done in SBRS||new 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|
|A26.65||DNR||2021-03-10||done||Peter to tag||DATA BETA: Last point for tagging dev version for integration of beta into ICU for changes that would affect ICU library code|
|A26.66||2021-03-10||done||Peter||Change the release page and cldr.org to say beta.|
|A26.67||2021-03-10||done||Rick||Send 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.
|A26.68||Finish Final Candidate||DNR||done||Steven/Peter > Peter||Tag as beta release with release-<major version>-beta, e.g: release-18-beta|
|A27||Finish Final Candidate||DNR||done||Kristi||Verify that all X blockers/critical are done (Except BRS task tickets)||Current version (v38) ALL-Filter 10094||https://unicode-org.atlassian.net/issues/?filter=10054|
|A27.13||DNR||done||Kristi||Readiness for Beta: All tickets other than spec, doc, BRS, and Charts are in Review or Done|
|A27.14.5||Post||NR||in progress||Missing components and tickets in review||Kristi||Clean 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 10129||https://docs.google.com/document/d/1VWmFU1twrFmp2met1Sw1Dwc4601DGuo437avkku4SQ0/edit#heading=h.6eubxgjrklef|
|A27.5||DNR||done||Kristi||Commit 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.
|A28||Finish Final Candidate||DNR||done, doc updated||Steven/Peter||Update ICU4J libraries in CLDR again (after ICU4J feature / code freeze & CLDR integration into ICU)||http://cldr.unicode.org/development/updating-icu-jar|
|A29||Finish Final Candidate||NR||done||Mark/Peter||Make 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.
|A31.5||DNR||moot||Steven||Push to Survey Tool Production at Beta.|
|A32.3||Finish Final Candidate||DNR||moot||Yoshito||Verify 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.
|A32.5||Finish Final Candidate||NR||done Peter, 24th late||Steven/Peter||Part 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.
|A33.1||DNR||moot||Mark||Rebuild the charts||http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts|
|A33.15||DNR||done||Mark||Compose blog post for beta|
|A33.2||Finish Final Candidate||NR||2021-03-25||done||Rick/Peter||SPEC 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.|
|A33.7||Finish Final Candidate||DNR||moot||Peter||Sync 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
|A34.5||Finish Final Candidate||DNR||done||Mark||Run GenerateDTD.java to write out DTD files in canonical form.|
|A34.7||Finish Final Candidate||NR||2021-04-02||done||Mark||Get the new/changed items for the release page.||http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts|
|A34.8||Finish Final Candidate||NR||moot||Mark||Generate 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|
|A35||Finish Final Candidate||NR||done||Mark/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!!
|B01||DNR||2021-04-02||done||Kristi/Steven||Commit checker run #3 (final): Run Shane's checker tool (Steven), verify results||https://gist.github.com/srl295/1e162778680d4a4b50ae802df1aa2d97|
|B02||Validate||NR||2021-04-05||moot||Mark||Make 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|
|B03||Validate||NR||in progress, generated beta 2 target mid-apr for final. Updated the release note with a link||Steven||Create JSON data (can generate from cldr-staging), and tag with appropriate release tag||https://sites.google.com/site/cldr/development/updating-codes/updating-json-data|
|B08||Validate||DNR||moot||Meike /Kherishma /Fredrik||Simple 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
|B10||DNR||2021-04-14||moot||Tom||Push to Survey Tool Production at pre-release, for sanity check|
|D01||Prepare final docs||DNR||2021-04-02||done||Rick||[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.|
|2021-03-31||done||Markdown spec fixes applied|
|D07.2||Prepare final docs||NR||2021-04-05||done||Mark/Peter||Prepare the announcement text for Rick to send out.||https://docs.google.com/document/d/1_o-mGZkUgt68KqOJVV4OOWDUUzuRjp5AgwoMIKnWQ0M/edit#heading=h.jbmfnmsf2wuz|
|D07.35||Prepare final docs||NR||2021-04-05||done||Mark||Make 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
|D07.37||Prepare final docs||NR||2021-04-05||moot||Mark / Peter||Fix the draft press-release page (also used for the notice).|
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.
|D07.38||Prepare final docs||DNR||2021-04-05||done||Rick||Remove the yellow from UTS#35 draft, and clean up everything for posting.|
THIS HAS TO BE FINAL! All links in spec.
|D07.4||Prepare final docs||NR||2021-04-07||done||Rick/Fredrik||Check all the links on the release page (link is example)||http://cldr.unicode.org/index/downloads/cldr-39|
|D08||Prepare final docs||NR||2021-04-07||done||Steven, 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.
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|
|E01||Post||DNR||2021-04-06||done||Peter||Update CLDR version information and links in readme.html for final release|