|Target EOD||Owner||Task Description||Bug/How-To Links||Other Links|
|Resolve Disputes/Errors ST||A01||DONE - n/a||all||Dispute Resolution - 0 errors in ST - or until determined that all remaining errors are konwn/documented.|
|Resolve Disputes/Errors ST||A02||DONE||2016-02-02||John||Review Known issues in Unit tests.|
|Resolve Disputes/Errors||A03||DONE||John||Run ConsoleCheckCLDR vs. vxml, distribute errors to be fixed; (with options: -e -z final_testing )||https://sites.google.com/site/cldr/cldr-22-data-resolution|
|Resolve Disputes/Errors||A04||DONE - n/a||John||Move data from ST to SVN trunk ; 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. )|
|Resolve Disputes/Errors||A05||DONE - n/a||John||Decide which locales have enough data to move from seed to common and move them.||https://docs.google.com/spreadsheet/ccc?key=0Aq1ZbpVosq6_dGg0MG1QMWJEU0hvaUxRbXJPQkVGY1E#gid=0|
|Resolve Disputes/Errors||A05.1||DONE - n/a||John||Analyze differences between en_GB and en_001, determine which data needs to move up and any necessary corrections to English.||https://docs.google.com/spreadsheets/d/1coDH7G7EImf3veoQeYUh0wInd8g90XCLe4xSNqU4WdM/edit#gid=0|
|Resolve Disputes/Errors||A06||DONE||John||Run ConsoleCheckCLDR vs. trunk, distribute errors to be fixed; (with options: -e -z final_testing - work the error count down to 0|
|Resolve Disputes/Errors||A06.1||DONE||John||Run the CLDR unit tests in exhaustive mode "-e10" or "ant unittestExhaustive", and fix any errors found.||THIS CAN BE REMOVED NOW THAT WE HAVE A BUILDBOT RUNNING IT REGULARLY|
|Resolve Disputes/Errors||A07||DONE||All||Work any manual data changes that need to go in before we attempt to freeze the main data||http://unicode.org/cldr/trac/report/80|
|Resolve Disputes/Errors||A08||DONE||John||Make sure all Subversion properties are correct.||I added a shell script to do this in tools/scripts/fixSVNProperties.sh|
|Resolve Disputes/Errors||A09||Mark||Update the plurals as per the link:||https://sites.google.com/site/cldr/development/updating-codes/update-plurals|
|Incorporate UCD||A09.1||moot until Unicode 9||Mark/Peter||Update for any new version of Unihan. The link at right needs some cleanup, but down the page talks about GenerateUnihanCollators, which is the tool that needs to be run.||http://cldr.unicode.org/development/development-process/design-proposals/unihan-data|
|Finish Supplemental Data||A10||*||DONE||John||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|
|Finish Supplemental Data||A11||DONE||2016-02-05||John||Update Language/Script/Region Subtags||http://cldr.unicode.org/development/updating-codes/update-languagescriptregion-subtags|
|Finish Supplemental Data||A11.1||2016-02-09||Mark||Update Subdivision Subtags||http://cldr.unicode.org/development/updating-codes/updating-subdivision-codes|
|Finish Supplemental Data||A11.2||in progress (need script update)||2016-02-09||Mark||Update attribute validity info (Mark to supply instructions...)|
MUST come after updating LSTR codes, currency, timezone, subdivisions, etc.
|Finish Supplemental Data||A11.3||DONE||2016-02-09||Mark||Do a diff of the current UCD nameslist annotations to look at deltas to see if anything should be added to English annotations for emoji.|
|Finish Supplemental Data||A12||DONE||2016-02-08||John||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|
|Finish Supplemental Data||A13||Peter||Verify the transforms with org.unicode.cldr.test.TestTransforms (tried at -e5).||No problems (needed to add to CLASSPATH: $ICU4J_ROOT/main/tests/translit/out/bin/)||http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts|
|Finish Supplemental Data||A14||*||DONE||John||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|
|Finish Supplemental Data||A15||*||DONE||John||Ensure UN codes are up to date, and the EU is up to date.||http://unstats.un.org/unsd/methods/m49/m49chang.htm||http://europa.eu/about-eu/countries/member-countries/index_en.htm|
|Finish Supplemental Data||A16||*||In Progress||Yoshito||Update the tzdata files and verify that bcp47 data is consistent with latest tzdata||https://sites.google.com/site/cldr/development/updating-codes|
(New instruction needed - new ticket - http://unicode.org/cldr/trac/ticket/8904)
|Finish Supplemental Data||A17||Peter||Manually sync over updates to ICU segment rules (GenerateSegments no longer really works). 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.|
|Finish Supplemental Data||A18||*||In Progress||John||Script Metadata, LikelySubtags||http://sites.google.com/site/cldr/development/updating-codes/likelysubtags|
|Finish Supplemental Data||A19||all||Complete all supplemental/collation/rbnf/transforms, etc.|
|Finish Supplemental Data||A20||Peter||Sync deprecated items: spec, DTD. (now just a spec thing, can move later)|
|Finish Final Candidate||A21||*||John||Run the necessary CLDRModify pases as outlined in:|
Should be rerun whenever we make significant data changes. (For LRS, abbreviate run as check).
|Finish Final Candidate||A22||John||Generate all algorithimically generated locales ( like sr_Latn and yo_BJ )||Run (and edit if necessary) tool/CLDRFileTransformer to generate transformed locales. Copy the generated xml files into common/main.|
|Finish Final Candidate||A23||John||Make sure de_CH overrides any inherited ß characters. (need to automate this)|
|Finish Final Candidate||A24||*||John/Peter||Verify that all of the key-type values in bcp47 directory and synchonized with validity data and with en.xml||File a ticket to add test for English|
|Finish Final Candidate||A25||*||Peter||Verify that all CLDR X reviews are done; nudge people to get them done or load balance. Make sure to look at both the Pending reviews and the Active tickets with code and no reviewer||http://unicode.org/cldr/trac/report/22||http://unicode.org/cldr/trac/report/27|
|Finish Final Candidate||A26||*||Steven||Verify that there is no code in the release that does not have a verified ticket for the release. (http://unicode.org/cldr/trac/report/51)||http://unicode.org/cldr/trac/report/51|
|Finish Final Candidate||A27||Peter||Verify that all X blockers/critical are done|
|Finish Final Candidate||A28||*||John||Move locales that don't have sufficiently good data to /seed/; Run ConsoleCheckCLDR, with options: |
-z final_testing -e
|Finish Final Candidate||A28.1||John||Update ICU4J libraries in CLDR||http://cldr.unicode.org/development/updating-icu-jar|
|Finish Final Candidate||A29||*||Peter||Make sure errata are taken care of.|
Delete any items that are taken care of.
File a bug on any item that is not.
|Finish Final Candidate||A30||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.|
|Finish Final Candidate||A31||Rick to get list; Peter to edit into web page||* Get contributors for http://cldr.unicode.org/index/acknowledgments|
get list of those who contributed through Survey tool (Login as TC, under 'Manage Users', click 'Email Address of Users Who Participated' (shows all users, not just your org)
* Get bug reporters and bug committers also.
* Send a message out 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.
|Finish Final Candidate||A32||Peter||Update CLDR version information and links in readme.html, update licenses? for candidate|
|Finish Final Candidate||A33||John||Tag alpha release with release-<major version>-<minor version>-d01, e.g: release-1-8-d01.|
|Finish Final Candidate||A34||*||Peter||Compare the DTDs to find out changes. Need to compare /common/dtd/* except for cldrTest.dtd, ldmlICIR.dtd, ldmlICU.dtd, and ldmlOpenOffice.dtd, AND /keyboards/dtd/*.|
Assign spec documentation tasks for missing items. Also diff root and en to catch new values.
|Need to move D01-D03 should go before B01|
|Finish Final Candidate||A35||*||Peter/Mark|
(all review and edit)
|Review spec and bugs, and DTD, and produce a good summary of the high points for the release page and press release.|
Make sure to supply a detailed Migration section, and a good "selling points" summary.
Generate the graphs for inclusion in the release page (see link in column H)
|Validate||B01||*||John||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.
|Validate||B02||*||Mark/John||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|
|Validate||B03||John||Create JSON data||https://sites.google.com/site/cldr/development/updating-codes/updating-json-data|
|Validate||B06||*||Yoshito||Organize import statements in Java source code|
|Validate||B07||*||John||Run unittest/TestBasic/TestBasicDtdCompatibility, with -DoldCommon=<wherever you have last release>|
eg -DoldCommon="/Users/Markdavis/Google Drive/Backup-2012-10-09/Documents/indigo/cldr-archive/cldr-22.0/common"
|This is part of the regular unit test suite in exhaustive mode.|
|Validate||B08||John||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||http://st.unicode.org/smoketest/v#/de/Languages_K_N/|
|Tag final candidate||C01||Peter||Update CLDR version information and links in readme.html for release|
|Tag final candidate||C02||John||Tag beta release with release-<major version>-<minor version>-d02, e.g: release-1-8-d02. No more changes without committee permission - The ICU tests in item B01 must be passing before this is tagged..|
|Prepare final docs||D01||Rick||Do preliminary scan of the spec for broken links, and other problems. Distribute to others to review/fix.||Copy the latest SVN 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.|
|Prepare final docs||D04||*||Mark||Cleanup spec HTML.|
Run CheckHtmlFiles and format.
See link to right for details.
|Prepare final docs||D05||Mark, Peter||Update the release page to include significant Modification items from the spec. This is a continuation of A35, but couldn't be completed until D04 is done.||http://cldr.unicode.org/index/downloads/cldr-27|
|Prepare final docs||D06||Mark||To get the number of items change/added: |
- add new directory for final data for cldr-xxxx. Include both common/ and keyboard/
- update GenerateItemCounts to add "cldr-xxxx", (the last version), and remove the oldest version (leaving 2).
- Make sure you set -DARCHIVE to point to the place where the archived directories are.
- run first with no arguments,
- then with the argument "-s".
Results will be in Generated/cldr/itemcount/summary.txt, and locales.txt.
- rerun with -s -d main to get the items in main.
- Get the items from the summary.txt file to generate differences in counts/percentages, and past into the spreadsheet to the right. This is to get the "X% more data" for the release page.
|Prepare final docs||D07||*||Rick||Prepare the final CLDR site pages|
http://cldr.unicode.org/index/downloads/cldr-28 (or whatever).
Note: these can't be finalized until the data and spec are final, see below.
Procedure for getting the URL for all fixed bugs for the release:
1. Change the milestone in the link: http://unicode.org/cldr/trac/query?status=closed&status=reviewing&resolution=fixed&group=component&max=999&col=id&col=summary&milestone=28
2. Make that the value for the Δ28 at the top of the release page. Make sure it opens in new page.
Hit enter to verify that it works.
|Prepare final docs||D07.1||*||Mark/John||Make sure the charts are all built with the *final* data, removing the "beta" tag, as per Generating Charts:||http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts|
|Prepare final docs||D08||*||Rick||Sanity-check all the above pages in step D7:|
all links work
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.
|Prepare final docs||D09||*||Rick||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-1-7-1
Fix the dates and versions throughout (don't forget the page title)
This step depends on D2 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.
|Prepare final docs||D10||*||Rick||Remove the yellow from UTS#35 draft, and clean up everything for posting.|
THIS HAS TO BE FINAL!
|Post||E01||Peter||Update CLDR version information and links in readme.html for final release|
|Post||E02||*||John||Create zip files from the tagged directories common and tools directories, with the tag (e.g: release-1-3) and post to site for Rick to pick up.||1). Go to cldr/tools and modify the version number in build.xml to the current version. 2). do "ant all" from the cldr/tools directory to create the zip files 3). Upload to unicode.org and notify Rick.|
|Post||E03||*||Rick||Create a new directory, eg http://unicode.org/Public/cldr/28/ and populate with zip files...||http://cldr.unicode.org/development/brs-post-items#E03|
|Post||E04||*||Rick||Update link to "latest"...||http://cldr.unicode.org/development/brs-post-items#E04|
|Post||E05||*||Rick||Change the chart redirects to point to the new versions...||http://cldr.unicode.org/development/brs-post-items#E05|
|Post||E06||*||Rick||Verify that the links on the release page...||http://cldr.unicode.org/development/brs-post-items#E06|
|Post||E07||*||Rick||Modify http://sites.google.com/site/cldr/index/downloads with new row on top...||http://cldr.unicode.org/development/brs-post-items#E07|
|Post||E08||*||Rick||Change dtd redirection, in /home/httpd/htdocs/cldr/dtd/.htaccess ...||http://cldr.unicode.org/development/brs-post-items#E08|
|Post||E09||*||Rick||Update https://sites.google.com/site/cldr/index/charts and other pages ...||http://cldr.unicode.org/development/brs-post-items#E09|
|Post||E10.1||*||John||Review and handle all X bugs connected with the final release process|
|Post||E10.2||*||John||Per SRL: "Make sure everyone has closed their bugs… then close the milestone." [Only after all reviews are done, & F1 & E4!] See: http://unicode.org/cldr/trac/roadmap|
|Tag final candidate||E11||*||John||Tag final release with release-<major version>-<minor version>, e.g: release-1-8. Make sure that LDML / TR35 is final first.|
Make sure to tag everything under cldr/: including common/, keyboards/, seed/, specs/, tools/ and licences/readme.
|Tag final candidate||E12||*||John||Move the tag for latest. (New)|
|Post||E13||*||Rick||Update the sidebar for the release...||http://cldr.unicode.org/development/brs-post-items#E13|
|Post||E14||*||Rick||Create a new blog page...||http://cldr.unicode.org/development/brs-post-items#E14|
|Post||E15||*||Rick||Prep and send announcement...||http://cldr.unicode.org/development/brs-post-items#E15|
|Post||E16||*||Rick||Verify that reports 22, 51, 52 is empty before trunk opens... and send "trunk open" message...||http://cldr.unicode.org/development/brs-post-items#E16|
|Prepare for next release||F01||*||John||Regenerate beta charts for next release; follow Generating Charts.||http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts|
|Prepare for next release||F02||Rick||create a new stub release page for the next release, and update the pages:|
|Copy the previous page and state that it's a stub. Yellow some sections for the update|
|Prepare for next release||F03||*||Rick||Create the draft TR35 for next version and check into SVN so it's open for updates.||Typical bug subject = Prepare TR35 spec files for CLDR NN proposed update|
|Prepare for next release||F04||John||Update all of the "CURRENT" reports in trac to point to the new current milestones. Include report 62 and 63 as well.|
|Prepare for next release||F05||John||Update GEN_VERSION in CLDRFile.java to next milestone; update dtd versions|
|Prepare for next release||F06||Steven||Copy all voting data into accessable form before revising ST.|
|Prepare for next release||F07||John||Update ST to new version number and previous version number.|
Push latest ST code and data from smoketest (trunk) to production.
Verify that votes and alternate data from previous release are available. Put smoketest in BETA mode.
|F08||Peter||Update the acknowledgements page with the new contributors, sort, etc, and post.|
|Prepare for next release||F09||John||Remove / deprecate items that fall outside of the retention policy: Metazones - 20 years - Language / Territory translations: 5 years after deprecated in IANA subtag registry.|
Put the rules into a Sites page and point to it from here.
|https://docs.google.com/spreadsheet/ccc?key=0Aq1ZbpVosq6_dGs3VkFNLXBtemlkNVpaOUxtajN4a1E#gid=0||CLDR Data Retention Policy|
|Prepare for next release||F10||John||Update CLDR's jars to latest version of ICU - guava - gson|
|Prepare for next release||F10.1||John||modify cldr-unittest/build.xml to use -z build instead of -z final_testing on the datacheck target - ( ST releases only... )|
|Prepare for next release||F10.2||John||Run the CLDRModify passes against the data before opening ST.||http://cldr.unicode.org/development/cldr-big-red-switch/cldrmodify-passes|
|Prepare for next release||F11||Mark||(Fall Release Versions) File bug and update scriptmetadata for the new Unicode scripts (from beta)|
|Prepare for next release||F12||Mark||(Fall Release Versions) File bug to update ICU used in CLDR whenever it is updated for new Unicode beta or final.|
|Prepare for next release||F13||Yoshito/John||Do Formatting Java source code|
|Prepare for Data Submission||G01||John||Update languages/scripts, currencies, timezones - See updating codes.|
|Prepare for Data Submission||G01.1||All||Review the "8-point required for approval" list of locales in coverageLevels.xml and update as appropriate.|
|Prepare for Data Submission||G02||John||GenerateBirths||http://cldr.unicode.org/development/updating-english-root|
|Prepare for Data Submission||G03||Steven||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 Review>Priority Items; Open Review>Zones|
|Prepare for Data Submission||G04||Steven/John||Move production ST to SUBMIT mode||http://cldr.unicode.org/#TOC-General-Schedule-|