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

View only
Task#StatusOwnerTask DescriptionBug/How-To LinksOther Links
A01doneallDispute Resolution - 0 errors in ST - or until determined that all remaining errors are known/documented.
A01.2doneallTake care of all flagged items.
A01.5doneMarkDo the tooling to copy /main/ subdivisions to subdivisions (and remove)Run -a
A02mootJohn/MarkReview Known issues in Unit tests (as logged when running the tests).
A03doneMark/John/PeterChange 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. )
A03.5doneMarkST is closed and read-only. Send message to ICU, cldr-dev
A04mootJohn/MarkDownload from ST into vxml (must be done after A03 to avoid losing data!!)admin-OutputAllFiles.jsp
A04.2mootJohn/MarkRun ConsoleCheckCLDR vs. vxml, distribute errors to be fixed; (with options: -e -z final_testing )
A04.5doneMark/John/PeterMove data from ST to SVN trunk (copying from vxml).
A05mootJohn/MarkGenerate a spreadsheet with recommendations for which locales have enough data to move from seed to common or vice versa. Bring to committee to make decision, and implement.
A05.3donePeterAfter item above, generate list of possible new locales for ICU and distribute to icu-core for discussion/approval before ICU integration.
A05.5doneJohn/Peter/MarkRun 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.7moot, no changes need promotingJohn/MarkAnalyze differences between en_GB and en_001 (main and annotations), determine which data needs to move up to en_001 and any necessary corrections.
A06doneMarkRun ConsoleCheckCLDR vs. trunk, distribute errors to be fixed; (with options: -e -z final_testing - work the error count down to 0
A06.1mootJohn/PeterUpdate ICU4J libraries in CLDR (will help with items afterwards)
A06.5doneAllWork any manual data changes (that affect ICU!!) that need to go in before we attempt to freeze the main data.
A06.7doneAllCheck the report "Active Tickets with Code and No Reviewer On Trunk" Ideally everything should be in review except items with Component=BRS.
A07.1done, Feb 18MarkSend out note to ICU, cldr-dev about data freeze (for all manual changes). Data needs to be stable for the production phases leading up to Alpha.
A07.1adone Feb 20John/Peter > PeterUpdate ICU4J libraries in CLDR (will help with items afterwards) (if not done above)
A07.2new itemJohn/PeterUpdate to latest version of guava and gson libs, if not done in SBRS
A07.2doneMarkRun to write out DTD files in canonical form. Writes in to {generated} directory. Diff and check in.
A08doneJohnMake sure all Subversion properties are correct.I added a shell script to do this in tools/scripts/
A09doneMarkUpdate the plurals as per the link:
A09.1doneMarkus/Peter/MarkUpdate for any new version of Unihan, running
A10done; updated unicodeVersion, others already doneJohn/PeterMake 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
A11doneMarkUpdate Language/Script/Region Subtags (check for likelysubtags coming from exemplars)
A11.15moot, last update Aug 2018. Rerun GenerateValidity if changesJohn > Peter to tryMake sure that currencies are updated: see Updating Codes
A11.3doneMark/PeterAdd any necessary annotations and collation info for candidates for the next Unicode Version.
A12doneJohnUpdate supplemental data language/country/population from the spreadsheet, and do ConvertLanguageData.
A13mootPeter, MarkDOES NOT WORK CURRENTLY BECAUSE OF ICU4J JUnit changes, can only test transforms via ICU integration. Old notes: Verify the transforms with org.unicode.cldr.test.TestTransforms (e.g. at -e5). Enhancements needed per cldrbugs #9266 (DONE), #9267, #9268 to handle e.g. "t". need to add to CLASSPATH: $ICU4J_ROOT/main/tests/translit/out/bin/
A14doneMark/JohnEnsure UN codes are up to date, and the EU is up to date.
A15mootJohn/MarkIf there are any currency or region changes from (A14, A11), send notice to cldr-users; record on release page.
A16mootYoshitoUpdate 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)
(New instruction needed - new ticket -
A18doneMark/JohnScript Metadata (only for new Unicode), LikelySubtags. (LikelySubtags requires A12)
A18.5done (except subdivisions, will do that later)MarkUpdate attribute validity info
MUST come after updating LSTR codes, currency, timezone, subdivisions, etc.
A19doneMark• Update emoji collation (run, emoji annotations based on ESC recommendations.
A21doneJohn/MarkGenerate all algorithimically generated locales (like sr_Latn, de_CH. and yo_BJ, and new ha_NE ). Remember to do all of (main, annotations, subdivisions).Run (and edit if necessary) tool/CLDRFileTransformer to generate transformed locales. Copy the generated xml files into common/{main, annotations, subdivisions}.
NOTE: Need to re-run each modified file in (main, annotations, subdivisions) through CLDRModify -fp and -r after generation!
Can be done with filter, eg (but update list!!)
A22.5doneMark/John• Generate the derived annotations with (Tool may need updates if there are new characters or RGI.)
• Run all the CLDRModify passes on derivedAnnotations folder to minimize the DerivedAnnotations
• Run RemoveEmptyCLDR to remove empty files in annotationsDerived
A23donePeter/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:
A23.5donePeterUpdate CLDR version information and links in readme.html, update licenses? for candidate
A23.52done (pending review from Andy)MarkRun 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.54moot Will happen in 35.1; not enough time to do in ICUAndy/PeterManually 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.4mootPeter/JohnRun the necessary CLDRModify passes as outlined in link.
Should be rerun whenever we make significant data changes. (For LRS, abbreviate run as check).
A24.6done Feb 21Peter/John/RickTag as release-35-alpha. Ready for ICU integration(Peter)
Send out note to cldr-dev that alpha is tagged. (before we have a complete spec ready). (John)
A33.1doneStevenRun script to identify locale code changes (trunk vs last-release). The relevant result should be added in the Release notes page.
A24.8donePeter/MarkGet minimal release page (eg ready for alpha. Should at least have overview section. Say on release page we are in alpha.
A25.2doneMarkUpdate Subdivision Subtags. If done after alpha, rebuild validity.
A25.4doneMarkUpdate Subdivision Translations. Need to do A21 again afterwards just for these.
A25.6doneMarkUpdate attribute validity info for subdivisions; regenerate ChartSubdivisionNames
A25.8doneMarkRebuild the charts (not gating item for alpha).
A26done Feb 27Peter/John/RickPublic announcement of alpha - tagged as alpha2
Change the release page and the main page Status to say Alpha.
Send notice in email to cldr-users, unicore, unicode, icu-announce. (Peter)
Post also as blog announcement (using the summary text). Add link on release page and main page (on the world "Alpha") to the blog article. (Rick)
pre-alpha announcement tasks for pages:
A26.2doneALLDecide on final release manager: Peter
A26.4done for alpha2Peter/JohnIntegrate into ICU, fix issues.
A24.5moot (no dtd changes)MarkReview the suppressions in unittest/ (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.
A25donePetermonitor/noodge people for any data changes from reviews that need to go in before we attempt to freeze the main data
A26donePeterVerify that there is no code in the release that does not have a verified ticket for the release. (
A27donePeterVerify that all X blockers/critical are done (Except BRS task tickets)
A28doneJohn/Peter -> PeterUpdate ICU4J libraries in CLDR again (after ICU4J feature / code freeze & CLDR integration into ICU)
A29donePeter/MarkMake 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.
A31doneDoesn't block beta: Rick to get list; Peter to edit into web page* Get contributors for
get list of those who contributed through Survey tool (Login as TC or Admin, under "List Survey Tool Users, find 'Manage Users' then click 'Email Address of Users Who Participated' (shows all users, not just your org)
* Get bug reporters and bug committers also. See Available Reports in Trac and find list of reporters. (Reporters by Milestone, report 60, easy to edit out rows aside from current release milestones).
* Send a message out to those people who contributed at least one item, (see the
* This is NOT a blocker for the release; we can update that page at any time.
A3ndonePeterupdate readme for beta
A32.2doneMarkCompare 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/*.
Check, and (supplemental and bcp47).
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
A32.3doneYoshitoVerify that every BCP47 -u and -t extension key is documented in TR35 (file tickets for missing ones).We point to the description, so just important ones
A32.5donePeterTest 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.
A33doneJohn/Steven/Peter > PeterCreate maint branch, and tag as beta release with release-<major version>-beta, e.g: release-1-8-beta
A33.2done March 18Rick/PeterOnce the spec is mostly done, send out note about beta. See above under Alpha for details.
A33.7moot (no deprecations)PeterSync 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.5doneMarkRun to write out DTD files in canonical form.
A34.7doneMarkRun ChartDelta to get the new/changed items for the release page.
A34.8mootMarkGenerate the graphs for inclusion in the release page (see link), and add to release items.
(all review and edit) - in progress
Review bugs, significant Modification items from the spec,, 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!!
B02in progress, not a blockerMark/JohnMake sure the charts are all built with the latest data, as per Generating Charts:
B03doneJohn/StevenCreate JSON data
B04doneJohnMake sure all Subversion properties are correct (last time)I added a shell script to do this in tools/scripts/
B06doneYoshito/JohnOrganize import statements in Java source code
B08done - 3 different languagesFredrik /Kristi /Meike /JohnSimple 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
D00mootALLRecord the target days and hour of day in Targets; on release day times < 12PM PT.
D01doneRickDo 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.
D04mootMarkCleanup spec HTML.
Run CheckHtmlFiles and format.
See link to right for details.
(NOT showstopper for release)
D05moot - need better queryKristi/MarkVerify that the tickets have the right Milestone. Look at tickets closed after 34 that don't have 35 as milestone, for example.Create query and add link. No easy query is possible. For now, created:
Problems with this:
D07done - this is really a post-tag step, should move downPeter/FredrikPrepare the final CLDR site pages (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:
0. look at (with the milestone XXXX fixed). Address any with status!=closed (or fix resoution)
0.5. look at, and set the component to the right value.
1. (???)Change the milestone in the link:
2. Make that the value for the Δ30 (or whatever) at the top of the release page. Make sure it opens in new page.
Hit enter to verify that it works.
Links may not all work until the directories and tags are in place below.
D07.2doneMark/PeterPrepare the announcement text for Rick to send out.
D07.5in progress
not showstopper
(Built on March 22)
Mark/JohnMake sure the charts are all built with the *final* data, removing the "beta" tag, as per Generating Charts:
(NOT showstopper for release)
D08donePeter, RickSanity-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.
D09donePeter / MarkFix the draft press-release page (also used for the notice).
In particular:
update the most recent boilerplate About Unicode from Ellen
replace the body by a summary of the release note, eg
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.
D09.5doneMark, PeterPrepare announcement
D10doneRickRemove the yellow from UTS#35 draft, and clean up everything for posting.
E01donePeterUpdate CLDR version information and links in readme.html for final release
E01.5doneJohn, PeterTag final release (from maint branch) 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.
svn copy svn+ssh:// svn+ssh:// --parents -m 'cldrbug 11037: copy tags/release-33-1-d04 to tags/release-33-1'
E02doneJohn/ Steven/ PeterCreate 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 and notify Rick.
E03doneRickCreate a new directory, eg and populate with zip files...
E04doneRickUpdate server link to "latest"...
E05doneRickChange the chart redirects to point to the new versions...
E06doneRickVerify that the links on the release page work... And update "news" at top of home page
E07doneRick / PeterModify with new row on top...
E08doneRickChange dtd redirection, in /home/httpd/htdocs/cldr/dtd/.htaccess ...
E09doneRickUpdate and other pages ...
E12donePeterMove the SVN tag for latest. (New)Copy svn release tag to "latest"
E14doneRickCreate a new blog page based on the draft press release... and prep the home page update line for the release...