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

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
Task# LRSTarget EODStatusOwnerTask DescriptionBug/How-To LinksOther Links
2
A01Resolve Disputes/Errors STdoneallDispute Resolution - 0 errors in ST - or until determined that all remaining errors are known/documented.
3
A02Resolve Disputes/Errors STdoneJohn/MarkReview Known issues in Unit tests (as logged when running the tests).
4
A03Resolve Disputes/ErrorsdoneJohn/MarkRun ConsoleCheckCLDR vs. vxml, distribute errors to be fixed; (with options: -e -z final_testing )https://sites.google.com/site/cldr/cldr-22-data-resolution
5
A04Resolve Disputes/ErrorsDONEJohnMove 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. )
6
A05Resolve Disputes/ErrorsmootJohn/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.https://docs.google.com/spreadsheet/ccc?key=0Aq1ZbpVosq6_dGg0MG1QMWJEU0hvaUxRbXJPQkVGY1E#gid=0
7
A05.3Resolve Disputes/ErrorsmootPeterAfter item above, generate list of possible new locales for ICU and distribute to icu-core for discussion/approval before ICU integration.
8
A05.5Resolve Disputes/Errors*2018-02-07doneJohn/PeterRun the necessary CLDRModify passes as outlined in:
http://cldr.unicode.org/development/cldr-big-red-switch/cldrmodify-passes
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
9
A05.7Resolve Disputes/ErrorsdoneJohn/MarkAnalyze differences between en_GB and en_001, determine which data needs to move up and any necessary corrections to English. (Fall releases only)https://docs.google.com/spreadsheets/d/1coDH7G7EImf3veoQeYUh0wInd8g90XCLe4xSNqU4WdM/edit#gid=0
10
A06Resolve Disputes/ErrorsdoneJohnRun ConsoleCheckCLDR vs. trunk, distribute errors to be fixed; (with options: -e -z final_testing - work the error count down to 0
11
A6.1Resolve Disputes/ErrorsdoneJohn/PeterUpdate ICU4J libraries in CLDR (will help with items afterwards)http://cldr.unicode.org/development/updating-icu-jar
12
A07Resolve Disputes/Errors2018-02-15doneAllWork any manual data changes that need to go in before we attempt to freeze the main datahttp://unicode.org/cldr/trac/report/80
13
A07.1Resolve Disputes/ErrorsdoneMarkSend out note about data freeze to ICU
14
A07.2Resolve Disputes/ErrorsdoneMarkRun GenerateDTD.java to write out DTD files in canonical form. Writes in to {generated} directory. Diff and check in.
15
A08Resolve Disputes/ErrorsdoneJohnMake sure all Subversion properties are correct.I added a shell script to do this in tools/scripts/fixSVNProperties.sh
16
A09Resolve Disputes/Errorsdone, added to release pageMarkUpdate the plurals as per the link: https://sites.google.com/site/cldr/development/updating-codes/update-plurals
17
A09.1Incorporate UCDmootMark/PeterUpdate for any new version of Unihan, running GenerateUnihanCollators.java.http://cldr.unicode.org/development/development-process/design-proposals/unihan-data
18
A10Finish Supplemental Data*doneJohnMake 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
19
A11Finish Supplemental DatadoneMarkUpdate Language/Script/Region Subtags (check for likelysubtags coming from exemplars)http://cldr.unicode.org/development/updating-codes/update-languagescriptregion-subtags
20
A11.1Finish Supplemental DatadoneMarkUpdate Subdivision Subtagshttp://cldr.unicode.org/development/updating-codes/updating-subdivision-codes
21
A11.1Finish Supplemental Datamoot, not this releaseMarkUpdate Subdivision Translationshttp://cldr.unicode.org/development/updating-codes/updating-subdivision-translations
22
A11.15Finish Supplemental Data*doneJohnMake sure that currencies are updated: see Updating Codeshttps://sites.google.com/site/cldr/development/updating-codes/update-currency-codeshttp://cldr.unicode.org/development/updating-codes
23
A11.3Finish Supplemental DatamootMark/PeterAdd any necessary annotations and collation info for candidates for the next Unicode Version.
24
A12Finish Supplemental DatadoneJohnUpdate supplemental data language/country/population from the spreadsheet, and do ConvertLanguageData.https://sites.google.com/site/cldr/development/updating-codes/update-language-script-info
25
A13Finish Supplemental DatamootPeter, 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/http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
http://cldr.unicode.org/development/cldr-big-red-switch/testing-transforms
26
A14Finish Supplemental Data*doneMark/JohnEnsure 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.htm
27
A15Finish Supplemental Data*doneJohn/MarkIf there are any currency or region changes from (A14, A11), send notice to cldr-users; record on release page.
28
A16Finish Supplemental Data*mootYoshitoUpdate 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)
29
A18Finish Supplemental Data*doneMark/JohnScript Metadata (only for new Unicode), LikelySubtags. (LikelySubtags requires A12)https://sites.google.com/site/cldr/development/updating-codes/updating-script-metadatahttp://sites.google.com/site/cldr/development/updating-codes/likelysubtags
30
A18.5Finish Supplemental DatadoneMarkUpdate attribute validity info
MUST come after updating LSTR codes, currency, timezone, subdivisions, etc.
https://sites.google.com/site/cldr/development/updating-codes/update-validity-xml
31
A19Finish Supplemental Data*moot, will sync in JuneMark• Update emoji collation (run EmojiOrder.java), emoji annotations based on ESC recommendations.
32
A20Finish Supplemental Datamoot, will sync in JuneMarkRun Segment.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.
33
A20.5Finish Supplemental Datamoot, will sync in JunePeter/AndyManually 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.
34
A21Finish Final Candidate*doneJohn/PeterRun 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
35
A22Finish Final CandidatedoneJohn/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!!)
-s${workspace_loc}/cldr/common/annotations
-fp
-m(de_CH|ha_NE|sr_Latn_BA|sr_Latn_ME|sr_Latn_XK|sr_Latn|yo_BJ|yue_Hans)
http://unicode.org/cldr/trac/ticket/9516#comment:6
36
A22.5Finish Final Candidatedone (whew)Mark/John• Call RemoveEmptyCLDR to remove empty files in annotations
• Run CLDRModify -fQ -s${workspace_loc}/cldr/common/annotations to add names to keywords

• Generate the derived annotations with GenerateDerivedAnnotations.java. (Tool may need updates if there are new characters or RGI.)
• Run cldrModify -r to minimize the DerivedAnnotations
• Call RemoveEmptyCLDR to remove empty files in annotationsDerived
37
A24Finish Final Candidate*moot, no BCP47 changes since CLDR 32PeterVerify 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
38
A24.05donePeter/MarkGet minimal release page (eg http://cldr.unicode.org/index/downloads/cldr-33) ready for alpha. Should at least have overview section. Also make sure charts are up to date (but not gating item). Say on release page we are in alpha.
39
A24.1Finish Final Candidate*donePeter/John/RickTag as release-33-alpha. (John)
Send out note about alpha (before we have a complete spec ready). (John)
Summarize release page in email to cldr-users, unicore, unicode, icu-announce. (Peter)
Post also as blog announcement. Add link on release page (on the world "Alpha") to the blog article. Change status in News table on cldr.org to be Alpha. (Rick)
pre-alpha announcement tasks for pages: http://cldr.unicode.org/development/brs-post-items#A24-1
40
A33.5Finish Final Candidate*doneALLDecide on final release manager
41
A24.2Finish Final CandidatedonePeter/JohnIntegrate into ICU, fix issues.
42
A24.5Finish Final CandidatedoneMarkReview 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.
43
A25Finish Final Candidate*donePetermonitor/noodge people for any data changes from reviews that need to go in before we attempt to freeze the main datahttp://unicode.org/cldr/trac/report/22http://unicode.org/cldr/trac/report/27
44
A26Finish Final Candidate*doneMarkVerify 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
45
A27Finish Final CandidatedonePeterVerify that all X blockers/critical are done (Except BRS task tickets)
46
A28Finish Final CandidatedoneJohn/PeterUpdate ICU4J libraries in CLDR again (after ICU4J feature / code freeze & CLDR integration into ICU)http://cldr.unicode.org/development/updating-icu-jar
47
A29Finish Final Candidate*donePeterMake 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://sites.google.com/site/cldr/errata
48
A31Finish Final CandidatedoneRick 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 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.
* 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.
http://cldr.unicode.org/development/cldr-big-red-switch
49
A32Finish Final CandidatedonePeterUpdate CLDR version information and links in readme.html, update licenses? for candidate
50
A32.2Finish Final Candidate*fridaydoneMarkCompare 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 http://www.unicode.org/cldr/charts/dev/supplemental/dtd_deltas.html, and http://www.unicode.org/cldr/charts/dev/delta/index.html (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 B01http://www.unicode.org/cldr/charts/dev/supplemental/dtd_deltas.html
51
A32.3Finish Final CandidatedoneYoshitoVerify that every BCP47 -u and -t extension key is documented in TR35 (file tickets for missing ones).
52
A32.5Finish Final Candidate*done, no change to ICU dataPeterTest 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.
53
A33Finish Final CandidatedoneJohn/Steven/PeterTag beta release with release-<major version>-beta, e.g: release-1-8-beta
54
A33.2Finish Final Candidate*doneRickOnce the spec is mostly done, send out note about beta. See above under Alpha for details.
55
A33.7Finish Final CandidatedonePeterSync 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?
56
A34.5Finish Final CandidatedoneMarkRun GenerateDTD.java to write out DTD files in canonical form.
57
A34.7Finish Final Candidate*doneMarkRun ChartDelta to get the new/changed items for the release page.
58
A34.8Finish Final Candidate*mootMarkGenerate the graphs for inclusion in the release page (see link), and add to release items.http://cldr.unicode.org/development/showlocalecoverage
59
A35Finish Final Candidate*2018-03-22donePeter/Mark
(all review and edit)
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!!
60
B02Validate*doneMark/JohnMake 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
61
B03ValidatedoneJohn/StevenCreate JSON datahttps://sites.google.com/site/cldr/development/updating-codes/updating-json-data
62
B06Validate*2018-03-22doneJohn/YoshitoOrganize import statements in Java source code
https://sites.google.com/site/cldr/development/eclipse-setup?pli=1#TOC-Clean-Up-Source-Code
63
B08ValidatedoneFredrik /Kristi /Chiara /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 ->ZonesFredrik: this seems off: http://cldr-smoke.unicode.org/smoketest/v#/de/Compact_Decimal_Formatting/5825fdcd5f32c291 (JCE) I think it is OK - this was manually changed after ST closed. See https://unicode.org/cldr/trac/ticket/10951 http://st.unicode.org/smoketest/v#/de/Languages_K_N/
64
D00Prepare final docsmootALLRecord the target days and hour of day in Targets; on release day times < 12PM PT.
65
D01Prepare final docsDONERickDo 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.
66
D04Prepare final docs*2018-03-22done enough for releaseMarkCleanup spec HTML.
Run CheckHtmlFiles and format.
See link to right for details.
(NOT showstopper for release)
https://sites.google.com/site/cldr/cleaning-up-the-spec
67
D07Prepare final docs*donePeter/FredrikPrepare the final CLDR site pages
http://cldr.unicode.org/index/downloads/cldr-30 (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 http://unicode.org/cldr/trac/query?resolution=fixed&milestone=XXXX&group=status&max=999 (with the milestone XXXX fixed). Address any with status!=closed (or fix resoution)
0.5. look at http://unicode.org/cldr/trac/query?resolution=fixed&milestone=XXXX&component=unknown&max=999, and set the component to the right value. Look at http://unicode.org/cldr/trac/query?type=unknown&resolution=fixed&milestone=XXXX&max=999 and fix the
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 Δ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.
http://cldr.unicode.org/index/downloads
68
D07.1Prepare final docs*doneMark/JohnMake sure the charts are all built with the *final* data, removing the "beta" tag, as per Generating Charts:
(NOT showstopper for release)
http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
69
D08Prepare final docs*2018-03-22DONERickSanity-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.
plus: http://www.unicode.org/draft/reports/tr35/tr35.html
70
D09Prepare final docs*donePeterFix 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.
http://sites.google.com/site/cldr/development/cldr-big-red-switch/draft-press
71
D10Prepare final docs*doneRickRemove the yellow from UTS#35 draft, and clean up everything for posting.
THIS HAS TO BE FINAL!
http://cldr.unicode.org/development/brs-post-items#D10
72
E01PostdonePeterUpdate CLDR version information and links in readme.html for final release
73
E01.5Tag final candidate*doneJohnTag 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.
74
E02Tag final candidate*doneJohn/ Peter/ StevenCreate 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.
75
E03Post*DONERickCreate a new directory, eg http://unicode.org/Public/cldr/30/ and populate with zip files...http://cldr.unicode.org/development/brs-post-items#E03
76
E04Post*DONERickUpdate server link to "latest"...http://cldr.unicode.org/development/brs-post-items#E04
77
E05Post*DONERickChange the chart redirects to point to the new versions...http://cldr.unicode.org/development/brs-post-items#E05
78
E06Post*DONERickVerify that the links on the release page work...http://cldr.unicode.org/development/brs-post-items#E06
79
E07Post*DONERickModify http://sites.google.com/site/cldr/index/downloads with new row on top...http://cldr.unicode.org/development/brs-post-items#E07
80
E08Post*DONERickChange dtd redirection, in /home/httpd/htdocs/cldr/dtd/.htaccess ...http://cldr.unicode.org/development/brs-post-items#E08
81
E09Post*DONERickUpdate https://sites.google.com/site/cldr/index/charts and other pages ...http://cldr.unicode.org/development/brs-post-items#E09
82
E12Post*DONEPeterMove the SVN tag for latest. (New)Copy svn release tag to "latest"
83
E14Post*DONERickCreate a new blog page based on the draft press release... and prep the home page update line for the release...http://cldr.unicode.org/development/brs-post-items#E14
84
E15Post*DONERickPrep and send announcement... http://cldr.unicode.org/development/brs-post-items#E15
85
E15Post*DONERickSend "trunk open" message... (Right after announcement is sent)(No longer depends on report closure)
86
E15.2Post*DONEPeter/JohnReview https://unicode.org/cldr/trac/report/51 and fix outliers.https://unicode.org/cldr/trac/report/51
87
E15.4Post*DONEPeter/JohnMake sure all reviews are done. Reviewers need to close old bugs, open new bugs if needed.https://unicode.org/cldr/trac/report/22
88
E16Prepare for next releasedonePeterUpdate the acknowledgements page with the new contributors, sort, etc, and post.
89
E17doneJohnPush final data from previous release to Survey Tool environment.
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Main
SBRS
 
 
Main menu