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

 
View only
 
 
Still loading...
ABCDEFGHIJK
1
seTask#LRSRC Task?Statusapprox.
Hours
Target EODOwnerTask DescriptionBug/How-To LinksOther Links
2
Resolve Disputes/Errors STA01DONEallDispute Resolution - 0 errors in ST - or until determined that all remaining errors are konwn/documented.
3
Resolve Disputes/Errors STA02DONEJohn/MarkReview Known issues in Unit tests (as logged when running the tests).
4
Resolve Disputes/ErrorsA03DONEJohnRun 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
Resolve Disputes/ErrorsA04DONEPeter/JohnMove 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
Resolve Disputes/ErrorsA05In Progress - Ready for TC ReviewJohn/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.https://docs.google.com/spreadsheet/ccc?key=0Aq1ZbpVosq6_dGg0MG1QMWJEU0hvaUxRbXJPQkVGY1E#gid=0
7
Resolve Disputes/ErrorsA05.1John/FredrikAnalyze 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
8
Resolve Disputes/ErrorsA06DONEJohnRun ConsoleCheckCLDR vs. trunk, distribute errors to be fixed; (with options: -e -z final_testing - work the error count down to 0
9
Resolve Disputes/ErrorsA072016-08-31AllWork any manual data changes that need to go in before we attempt to freeze the main datahttp://unicode.org/cldr/trac/report/80
10
Resolve Disputes/ErrorsA07.1MarkRun GenerateDTD.java to write out DTD files in canonical form.
11
Resolve Disputes/ErrorsA08John/StevenMake sure all Subversion properties are correct.I added a shell script to do this in tools/scripts/fixSVNProperties.sh
12
Resolve Disputes/ErrorsA09MarkUpdate the plurals as per the link: https://sites.google.com/site/cldr/development/updating-codes/update-plurals
13
Incorporate UCDA09.1Mark/PeterUpdate 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
14
Finish Supplemental DataA10*John/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.dtd
15
Finish Supplemental DataA11John/MarkUpdate Language/Script/Region Subtagshttp://cldr.unicode.org/development/updating-codes/update-languagescriptregion-subtags
16
Finish Supplemental DataA11.1MarkUpdate Subdivision Subtagshttp://cldr.unicode.org/development/updating-codes/updating-subdivision-codes
17
Finish Supplemental DataA11.2MarkUpdate 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
18
Finish Supplemental DataA11.3MarkDo a diff of the current UCD nameslist annotations to look at deltas to see if anything should be added to English annotations for emoji.
19
Finish Supplemental DataA12John/MarkUpdate supplemental data language/country/population from the spreadsheet, and do ConvertLanguageData.https://sites.google.com/site/cldr/development/updating-codes/update-language-script-info
20
Finish Final CandidateA12.5JohnUpdate ICU4J libraries in CLDR (will help with item A13)http://cldr.unicode.org/development/updating-icu-jar
21
Finish Supplemental DataA13Peter, MarkVerify the transforms with org.unicode.cldr.test.TestTransforms (tried at -e5). Enhancements needed per cldrbugs #9266, #9267, #9268 to handle e.g. "t", but tested in ICU and OK for now.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
22
Finish Supplemental DataA14*John/MarkMake 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
Finish Supplemental DataA14*John/MarkIf there are any currency or region changes from (A14, A11), send notice to cldr-users
24
Finish Supplemental DataA15*John/MarkEnsure UN codes are up to date, and the EU is up to date.http://unstats.un.org/unsd/methods/m49/m49chang.htmhttp://europa.eu/about-eu/countries/member-countries/index_en.htm
25
Finish Supplemental DataA16*YoshitoUpdate 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)
26
Finish Supplemental DataA17PeterManually 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.No changes to ICU rules so far in ICU 57
27
Finish Supplemental DataA18*JohnScript Metadata, LikelySubtagshttp://sites.google.com/site/cldr/development/updating-codes/likelysubtags
28
Finish Supplemental DataA19allComplete all supplemental/collation/rbnf/transforms, etc.
29
Finish Supplemental DataA20PeterSync deprecated items: spec, DTD. (now just a spec thing, can move later)
30
Finish Final CandidateA21*John/PeterRun the necessary CLDRModify pases 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
31
Finish Final CandidateA22Mark/JohnGenerate all algorithimically generated locales (like sr_Latn, de_CH. and yo_BJ )Run (and edit if necessary) tool/CLDRFileTransformer to generate transformed locales. Copy the generated xml files into common/main.
32
Finish Final CandidateA23Mark/JohnMake sure de_CH overrides any inherited ß characters. (should be done by A22, but check)
33
Finish Final CandidateA24*PeterVerify that all of the key-type values in bcp47 are in en.xmlFile a ticket to add test for English
34
Finish Final CandidateA25*PeterVerify 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/22http://unicode.org/cldr/trac/report/27
35
Finish Final CandidateA26*StevenVerify 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
36
Finish Final CandidateA27PeterVerify that all X blockers/critical are done
37
Finish Final CandidateA28John/PeterUpdate ICU4J libraries in CLDRhttp://cldr.unicode.org/development/updating-icu-jar
38
Finish Final CandidateA29*PeterMake sure errata are taken care of.

Delete any items that are taken care of.
File a bug on any item that is not.
http://sites.google.com/site/cldr/errata
39
Finish Final CandidateA30MarkReview 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.
40
Finish Final CandidateA31Rick 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.
http://cldr.unicode.org/development/cldr-big-red-switch
41
Finish Final CandidateA32PeterUpdate CLDR version information and links in readme.html, update licenses? for candidate
42
Finish Final CandidateA33John/StevenTag beta release with release-<major version>-<minor version>-d01, e.g: release-1-8-beta
43
Finish Final CandidateA33.5Mark/JohnSend note out that we are in beta
44
Finish Final CandidateA34*PeterCompare 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
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
45
Finish Final CandidateA34.1MarkRun GenerateDTD.java to write out DTD files in canonical form.
46
Finish Final CandidateA34a*MarkRun ChartDelta to get the new/changed items for the release page.
47
Finish Final CandidateA34b*MarkGenerate the graphs for inclusion in the release page (see link), and add to release items.http://cldr.unicode.org/development/showlocalecoverage
48
Finish Final CandidateA35*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. 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!!
49
ValidateB01*PeterTest 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.
50
ValidateB02*Mark/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
51
ValidateB03John/StevenCreate JSON datahttps://sites.google.com/site/cldr/development/updating-codes/updating-json-data
52
ValidateB06*YoshitoOrganize import statements in Java source code
https://sites.google.com/site/cldr/development/eclipse-setup?pli=1#TOC-Clean-Up-Source-Code
53
ValidateB08John /Fredrik /Kristi /KeumheeSimple 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 ->Zoneshttp://st.unicode.org/smoketest/v#/de/Languages_K_N/
54
Tag final candidateC01PeterUpdate CLDR version information and links in readme.html for release candidate
55
Tag final candidateC02John/StevenTag gamma 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..
56
Prepare final docsD01RickDo 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.
57
Prepare final docsD04*MarkCleanup spec HTML.
Run CheckHtmlFiles and format.
See link to right for details.
https://sites.google.com/site/cldr/cleaning-up-the-spec
58
Prepare final docsD05Mark, PeterUpdate 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
59
Prepare final docsD07*RickPrepare 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.
http://cldr.unicode.org/index/downloads
60
Prepare final docsD07.1*Mark/JohnMake 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
61
Prepare final docsD08*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.
plus: http://www.unicode.org/draft/reports/tr35/tr35.html
62
Prepare final docsD09*RickFix 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-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.
http://sites.google.com/site/cldr/development/cldr-big-red-switch/draft-press
63
Prepare final docsD10*RickRemove 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
64
PostE01PeterUpdate CLDR version information and links in readme.html for final release
65
PostE02*John/ 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.
66
PostE03*RickCreate a new directory, eg http://unicode.org/Public/cldr/29/ and populate with zip files...http://cldr.unicode.org/development/brs-post-items#E03
67
PostE04*RickUpdate link to "latest"...http://cldr.unicode.org/development/brs-post-items#E04
68
PostE05*RickChange the chart redirects to point to the new versions...http://cldr.unicode.org/development/brs-post-items#E05
69
PostE06*RickVerify that the links on the release page...http://cldr.unicode.org/development/brs-post-items#E06
70
PostE07*RickModify http://sites.google.com/site/cldr/index/downloads with new row on top...http://cldr.unicode.org/development/brs-post-items#E07
71
PostE08*RickChange dtd redirection, in /home/httpd/htdocs/cldr/dtd/.htaccess ...http://cldr.unicode.org/development/brs-post-items#E08
72
PostE09*RickUpdate https://sites.google.com/site/cldr/index/charts and other pages ...http://cldr.unicode.org/development/brs-post-items#E09
73
PostE10.1*JohnReview and handle all X bugs connected with the final release process
74
PostE10.2*JohnPer 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
75
Tag final candidateE11*JohnTag 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.
76
Tag final candidateE12*JohnMove the tag for latest. (New)
77
PostE13*RickUpdate the sidebar for the release...

http://cldr.unicode.org/development/brs-post-items#E13
78
PostE14*RickCreate a new blog page... and prep the home page update line for the release...http://cldr.unicode.org/development/brs-post-items#E14
79
PostE15*RickPrep and send announcement...http://cldr.unicode.org/development/brs-post-items#E15
80
PostE16*RickVerify that reports 22, 51, 52 is empty before trunk opens... and send "trunk open" message...http://cldr.unicode.org/development/brs-post-items#E16
81
Prepare for next releaseF01*JohnRegenerate beta charts for next release; follow Generating Charts.http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
82
Prepare for next releaseF02Rickcreate a new stub release page for the next release, and update the pages:
http://cldr.unicode.org/index/downloads/latest
http://cldr.unicode.org/index/downloads/beta
Copy the previous page and state that it's a stub. Yellow some sections for the update
83
Prepare for next releaseF03*RickCreate 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
84
Prepare for next releaseF04JohnUpdate all of the "CURRENT" reports in trac to point to the new current milestones. Include report 62 and 63 as well.
85
Prepare for next releaseF05JohnUpdate GEN_VERSION in CLDRFile.java to next milestone; update dtd versions
86
Prepare for next releaseF06StevenCopy all voting data into accessable form before revising ST.
/repos/cldr-aux
87
Prepare for next releaseF07JohnUpdate 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.
88
F08PeterUpdate the acknowledgements page with the new contributors, sort, etc, and post.
89
Prepare for next releaseF09JohnRemove / 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=0CLDR Data Retention Policy
90
Prepare for next releaseF10JohnUpdate CLDR's jars to latest version of ICU - guava - gson
91
Prepare for next releaseF10.1Johnmodify cldr-unittest/build.xml to use -z build instead of -z final_testing on the datacheck target - ( ST releases only... )
92
Prepare for next releaseF10.2JohnRun the CLDRModify passes against the data before opening ST.http://cldr.unicode.org/development/cldr-big-red-switch/cldrmodify-passes
93
Prepare for next releaseF11Mark(Fall Release Versions) File bug and update scriptmetadata for the new Unicode scripts (from beta)
94
Prepare for next releaseF12Mark(Fall Release Versions) File bug to update ICU used in CLDR whenever it is updated for new Unicode beta or final.
95
Prepare for next releaseF13Yoshito/JohnDo Formatting Java source code
96
Prepare for Data SubmissionG01JohnUpdate languages/scripts, currencies, timezones - See updating codes.
97
Prepare for Data SubmissionG01.1AllReview the "8-point required for approval" list of locales in coverageLevels.xml and update as appropriate.
98
Prepare for Data SubmissionG02JohnGenerateBirthshttp://cldr.unicode.org/development/updating-english-root
99
Prepare for Data SubmissionG03StevenSimple 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
100
Prepare for Data SubmissionG04Steven/JohnMove production ST to SUBMIT modehttp://cldr.unicode.org/#TOC-General-Schedule-
Loading...
 
 
 
Sheet1
Sheet2