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

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
|
 
Still loading...
ABCDEFGHIJ
1
seTask#LRSStatusapprox.
Hours
Target EODOwnerTask DescriptionBug/How-To LinksOther Links
2
Resolve Disputes/Errors STA01DONEallDispute Resolution - 0 errors in ST
3
Resolve Disputes/Errors STA02DONEJohnReview Known issues in Unit 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/ErrorsA04DONEJohnMove 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/ErrorsA05DONEJohnDecide 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
7
Resolve Disputes/ErrorsA06DONEJohnRun ConsoleCheckCLDR vs. trunk, distribute errors to be fixed; (with options: -e -z final_testing - work the error count down to 0
8
Resolve Disputes/ErrorsA06.1DONEJohnRun the CLDR unit tests in exhaustive mode "-e10" or "ant unittestExhaustive", and fix any errors found.
9
Resolve Disputes/ErrorsA07DONE2015-02-23AllWork 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/ErrorsA08DONEJohnMake sure all Subversion properties are correct.I added a shell script to do this in tools/scripts/fixSVNProperties.sh
11
Resolve Disputes/ErrorsA09DONEMarkUpdate the plurals as per the link: https://sites.google.com/site/cldr/development/updating-codes/update-plurals
12
Finish Supplemental DataA10*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.
13
Finish Supplemental DataA11DONEJohnUpdate Language/Script/Region Subtagshttp://cldr.unicode.org/development/updating-codes/update-languagescriptregion-subtags
14
Finish Supplemental DataA12DONEJohn 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
15
Finish Supplemental DataA13DONE*2015-02-25PeterVerify the transforms with org.unicode.cldr.test.TestTransforms (tried at -e5). * Test seems to have a problem and flags LAtin-Devanagari roundtrip failure for 0944/0962 (related to cldrbug 6940) but the same test works fine in ICU4J for this case when the updated transforms are integrated into ICU4J.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
16
Finish Supplemental DataA14*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
17
Finish Supplemental DataA15*DONEJohnEnsure 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
18
Finish Supplemental DataA16*DONEYoshitoUpdate the tzdata files and regenerate tzid list for supplementalMetaData.xml.
https://sites.google.com/site/cldr/development/updating-codes
19
Finish Supplemental DataA17DONE2015-02-28PeterGenerating segments. 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.http://cldr.unicode.org/development/updating-codes/generating-segments
20
Finish Supplemental DataA18*DONEJohnScript Metadata, LikelySubtagshttp://sites.google.com/site/cldr/development/updating-codes/likelysubtags
21
Finish Supplemental DataA19DONEallComplete all supplemental/collation/rbnf/transforms, etc.
22
Finish Supplemental DataA20DONE2015-02-28PeterSync deprecated items: spec, DTD comments, supplementalMetadata <deprecated> element: r11330, r11331
23
Finish Final CandidateA21*DONEJohnRun 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
24
Finish Final CandidateA22DONEJohnGenerate 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.
25
Finish Final CandidateA23DONEJohnMake sure de_CH overrides any inherited ß characters. (need to automate this)
26
Finish Final CandidateA24*DONE2015-03-04John/PeterVerify that all of the key-type values in bcp47 directory and synchonized with supplemental data.
27
Finish Final CandidateA25*DONEPeterVerify 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
28
Finish Final CandidateA26*DONEStevenVerify 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
29
Finish Final CandidateA27DONEPeterVerify that all X blockers/critical are done
30
Finish Final CandidateA28*DONE2015-02-27JohnMove locales that don't have sufficiently good data to /seed/; Run ConsoleCheckCLDR, with options:
-z final_testing -e
31
Finish Final CandidateA28.1DONEJohnUpdate ICU4J libraries in CLDRhttp://cldr.unicode.org/development/updating-icu-jar
32
Finish Final CandidateA29*DONEPeterMake 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
33
Finish Final CandidateA30DONEMarkReview the suppressions in unittest/TestLdml2ICU.java 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.
34
Finish Final CandidateA31DONE2015-03-12Rick 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
35
Finish Final CandidateA32DONE2015-03-04PeterUpdate CLDR version information and links in readme.html, update licenses? for candidate
36
Finish Final CandidateA33DONE2015-03-05JohnTag alpha release with release-<major version>-<minor version>-d01, e.g: release-1-8-d01.
37
Finish Final CandidateA34*DONEPeterCompare 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.
Need to move D01-D03 should go before B01
38
Finish Final CandidateA35*DONE2015-03-18Peter/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)
https://sites.google.com/site/cldr/development/showlocalecoverage
39
ValidateB01*DONE2015-03-06JohnTest 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.
40
ValidateB02*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
41
ValidateB03DONEJohnCreate JSON datahttps://sites.google.com/site/cldr/development/updating-codes/updating-json-data
42
ValidateB04*DONEallSpot-check for sanity (via charts and data)
43
ValidateB06*DONE2015-03-11YoshitoOrganize import statements and format Java source code
https://sites.google.com/site/cldr/development/eclipse-setup?pli=1#TOC-Clean-Up-Source-Code
44
ValidateB07*DONEJohnRun 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"
Need to make it a regular unit test.
45
ValidateB08DONEJohnSimple 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/
46
Tag final candidateC01DONE2015-03-12PeterUpdate CLDR version information and links in readme.html for release
47
Tag final candidateC02DONEJohnTag beta release with release-<major version>-<minor version>-d02, e.g: release-1-8-d02. No more changes without committee permission.release-26-d03
48
Tag final candidateC03DONEJohnTag gamma release with release-<major version>-<minor version>-d03, e.g: release-1-8-d03. No more changes without TC permission if something found via the chart review.
49
Prepare final docsD01DONE2015-03-13RickDo preliminary scan of the spec for broken links, and other problems. Distribute to others to review/fix.
50
Prepare final docsD04*DONE2015-03-16MarkCleanup spec HTML.
Run CheckHtmlFiles and format.
See link to right for details.
https://sites.google.com/site/cldr/cleaning-up-the-spec
51
Prepare final docsD05DONE2015-03-18Mark, 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
52
Prepare final docsD06DONE - moot2015-03-18MarkTo 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.
https://docs.google.com/spreadsheet/ccc?key=0AqRLrRqNEKv-dG5qZTg2UE5PNmNTZUhJWjR1eEQ4VkE#gid=6
53
Prepare final docsD07*DONERickPrepare the final CLDR site pages
http://cldr.unicode.org/index/downloads/cldr-27 (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=26
2. Make that the value for the Δ26 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
54
Prepare final docsD07.1*DONE2015-03-13Mark/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
55
Prepare final docsD08*DONE2015-03-18RickSanity-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
56
Prepare final docsD09*DONE2015-03-18RickFix 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
57
PostE01DONE2015-03-12PeterUpdate CLDR version information and links in readme.html for final release
58
PostE02*DONE2015-03-18JohnCreate 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.
59
PostE02.1*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#E02.1
60
PostE03*DONERickCreate a new directory, eg http://unicode.org/Public/cldr/27/ and populate with zip files...http://cldr.unicode.org/development/brs-post-items#E03
61
PostE04*DONERickUpdate link to "latest"...http://cldr.unicode.org/development/brs-post-items#E04
62
PostE05*DONERickChange the chart redirects to point to the new versions...http://cldr.unicode.org/development/brs-post-items#E05
63
PostE06*DONERickVerify that the links on the release page...http://cldr.unicode.org/development/brs-post-items#E06
64
PostE07*DONERickModify http://sites.google.com/site/cldr/index/downloads with new row on top...http://cldr.unicode.org/development/brs-post-items#E07
65
PostE08*DONERickChange dtd redirection, in /home/httpd/htdocs/cldr/dtd/.htaccess ...http://cldr.unicode.org/development/brs-post-items#E08
66
PostE09*DONERickUpdate https://sites.google.com/site/cldr/index/charts and other pages ...http://cldr.unicode.org/development/brs-post-items#E09
67
PostE10.1*DONEJohnReview and handle all X bugs connected with the final release process
68
PostE10.2*DONEJohnPer 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
69
Tag final candidateE11*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.
70
Tag final candidateE12*DONEJohnMove the tag for latest. (New)
71
PostE13*DONERickUpdate the sidebar for the release...

http://cldr.unicode.org/development/brs-post-items#E13
72
PostE14*DONERickCreate a new blog page...http://cldr.unicode.org/development/brs-post-items#E14
73
PostE15*DONERickPrep and send announcement...http://cldr.unicode.org/development/brs-post-items#E15
74
PostE16*DONE - Rpt 51 items verified/fixed by JohnRick 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
75
Prepare for next releaseF01*DONEJohnRegenerate beta charts for next release; follow Generating Charts.http://cldr.unicode.org/development/cldr-big-red-switch/generating-charts
76
Prepare for next releaseF02DONE2015-04-03Rickcreate 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
77
Prepare for next releaseF03*DONE2015-04-03RickCreate the draft TR35 for next version and check into SVN so it's open for updates.
78
Prepare for next releaseF04DONEJohnUpdate all of the "CURRENT" reports in trac to point to the new current milestones. Include report 62 and 63 as well.
79
Prepare for next releaseF05DONEJohnUpdate GEN_VERSION in CLDRFile.java to next milestone; update dtd versions
80
Prepare for next releaseF06DONE - n/aStevenCopy all voting data into accessable form before revising ST.
/repos/cldr-aux
81
Prepare for next releaseF07DONEJohnUpdate 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.
82
F08DONE2015-03-12PeterUpdate the acknowledgements page with the new contributors, sort, etc, and post.
83
Prepare for next releaseF09DONEJohnRemove / 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=0Territory "AN" should remove in CLDR 29
84
Prepare for next releaseF10DONEJohnUpdate CLDR's jars to latest version of ICU - guava - gson
85
Prepare for next releaseF10.1DONEJohnmodify cldr-unittest/build.xml to use -z build instead of -z final_testing on the datacheck target - ( ST releases only... )
86
Prepare for next releaseF11DONEMark(Fall Release Versions) File bug and update scriptmetadata for the new Unicode scripts (from beta)
87
Prepare for next releaseF12DONEMark(Fall Release Versions) File bug to update ICU used in CLDR whenever it is updated for new Unicode beta or final.
88
Prepare for Data SubmissionG01DONEJohnUpdate languages/scripts, currencies, timezones - See updating codes.
89
Prepare for Data SubmissionG01.1n/aAllReview the "8-point required for approval" list of locales in coverageLevels.xml and update as appropriate.
90
Prepare for Data SubmissionG02DONEJohnGenerateBirthshttp://cldr.unicode.org/development/updating-english-root
91
Prepare for Data SubmissionG03DONEStevenSimple 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
92
Prepare for Data SubmissionG04DONE2015-05-01Steven/JohnMove production ST to SUBMIT modehttp://cldr.unicode.org/#TOC-General-Schedule-
Loading...
 
 
 
Sheet1
Sheet2