Schedule (Tentative)

Date Phase
06.29
 1.7.1 Released
07.01
 1.8 Development starts
10.16 1.8 Data submission starts
12.02 1.8 Data submission ends - vetting starts
01.13 1.8 Data resolution, data/structure verification and correction starts
02.10 1.8 Final Candidate available
03.10 1.8 Target release date
For details, see Release Schedule.
See also Notification Services.

CLDR: Big Red Switch

Show What to do before we release for CLDR version X (eg X = 1.9):

All: remember to make sure that the target: X is set on all the X bugs, otherwise the Release Changes link won't pick them up.
Items marked * are for the "Little Red Switch": dot-dot releases (supplemental data, ids, timezones, small spec fixes). Items marked ** are only done for a LRS if there was a DTD change.
Phase Status Owner Task
Create Final Candidate
A1 DONE
 mark Incorporate the vetted data from the tool.
A2* DONE
 mark yoshito Make sure that all the external IDs are updated: see Updating Codes
A3 DONE
 mark Do Generating Segments
A4 DONE
mark Run ConsoleCheckCLDR, distribute errors to be fixed
(with options: -e -g -c minimal -z final_testing -DCLDR_DTD_CACHE=C:\cldrcache\ -Dfile.encoding=UTF-8 -DSHOW_FILES -Xmx512M)
A5 DONE
 john Run the necessary CLDRModify Passes
Should be rerun whenever we make significant data changes.
A6 Done
 pedberg Verify that all CLDR X reviews are done; nudge people to get them done or load balance
A6.1 DONE pedberg Verify that there is no code in the release that does not have a verified ticket for the release.
  1. http://www.unicode.org/cgi-bin/bugdiffs.pl/admintop?user=
  2. Put "release-1-2" into Start Tag
  3. Put "release-1-6" (or whatever it is) into End Tag
  4. Scroll to the bottom, click Reviewer Report
  5. Click NONE
  6. Anything open there is a problem
A7 DONE
 emmons Verify that all X showstoppers are done
A7a DONE emmons Spot check by-type charts for sanity.
A8* DONE
 emmons
 Remove locales that don't have sufficient data
  1. Run ConsoleCheckCLDR, with options: (mark to look at making chron job)
    • -f [a-z]+
    • -c minimal
    • -z final_testing
    • -t .*Coverage.*
  2. Review review locales that show up.
  3. Also remove the und.* locales
A9 DONE
 srl
 Get contributors for http://cldr.unicode.org/index/acknowledgments
  1. get list of those who contributed through Survey tool
    1. Steven to document how to get this data!
  2. send a message out to those people who contributed at least one item, (see the end of this page). This is NOT a blocker for the release; we can update that page at any time.
A10*
 DONE chris
 Make sure errata are taken care of.
http://sites.google.com/site/cldr/errata
  • Delete any items that are taken care of.
  • File a bug on any item that is not.
Validate
B1 DONE all For running all tools, clear DTD cache so that tools use the final DTD.
B2 DONE emmons
    1. Check that root.xml and en.xml contain no draft items
    1. Verify that there are no draft="true" items.
B3* DONE emmons Before finalizing, run ConsoleCheckCLDR to verify consistency
B4 DONE
 mark Rebuild the CLDR test data (common/test) by running org.unicode.cldr.tool.GenerateCldrTests. and then GenerateLikelySubtagTests.java, and check in. (note that it may run low on memory, and slow to a crawl. If so, run in sections, first with -m[a-m].*, then -m[n-u].*, then -m[v-z].*)
B4a DONE
 mark Verify the transforms with Testing Transforms
B5* Done emmons, loomis Test CLDR with ICU: Build ICU4C and ICU4J that uses the final candidate, verifying that the tests pass -- insofar as CLDR data is concerned
    1. This means running both the LDML2ICUConverter tool and the ConvertTransforms tool.
    2. Once done, run org.unicode.icu.org.TestCldr on the CLDR test data.
B6* DONE
 mark
 Make sure the charts are all built with the latest data, as per Generating Charts
B7 DONE emmons Spot-check for sanity (via charts and data)
B8 DONE mark Run Misc -i and review attribute values
B9 DONE mark Run FindDTDOrder a final time to verify that DTDs are reasonable.
B10 DONE all Repeat until tests pass and charts build
B11
 DONE
 emmons Generate POSIX and compile on some UNIX system.
Tag the final candidate
C1 DONE emmons Tag alpha release with release-<major version>-<minor version>-d01, e.g: release-1-3-d01.
C2 DONE emmons Tag beta release with release-<major version>-<minor version>-d02, e.g: release-1-3-d02.
C3* DONE
 emmons Tag final release with release-<major version>-<minor version>, e.g: release-1-3.
C4 DONE emmons Tag only the common, dtd, posix, test, and tools directories.
  1. Make sure to tag common/ collation, main, posix, segments, supplemental, test, and transforms
C5* DONE emmons Once tagged with the release-1-3, send email to the list saying that no more changes are to be checked into CVS! Once this message has gone out, do not check in any changes without permission!
Prepare final docs
D1* DONE
 mark

Review spec and bugs, and produce a good summary of the high points for the release page and press release.
D2* DONE
 mark Prepare the final CLDR site pages, plus the common/test/readme.html
  1. http://cldr.unicode.org/index/downloads/
  2. http://cldr.unicode.org/index/downloads/cldr-1-9 (or whatever)
Note: these can't be finalized until the data and spec are final, see below.
D3* DONE rick Sanity-check all the above pages in step D2:
  • all links work
  • all versions, tags, and dates are right
plus: http://www.unicode.org/draft/reports/tr35/tr35.html
D4 Done
 mark, chrish Update skeleton release pages with figures
  1. get the number of values with CountItems -Dmethod=countItems.
  2. Compare against previous release with CountItems -Dmethod=countItems -Dsource=C:\cvsdata\unicode\cldr\cldr_1_9\main (or equivalent source directory)
    1. This is to get the "X% more data" for the release page. Use average of unique values and unique full paths. For the number of items added, use the delta in total items.
  3. run GenerateCLDRTests -g to get locale info
    1. It will generate in C:/cvsdata/unicode/cldr/dropbox/gen/test/log.html
D5* DONE
 rick Fix the draft press-release page (also used for the notice).
In particular:
  • update the most recent boilerplate About Unicode from Magda
  • replace the body by a summary of the release note, eg http://cldr.unicode.org/index/downloads/cldr-1-7-1 into
  • fix the dates and versions throughout (don't forget the page title)
This step depends on D2 above.




Post
E1* Done emmons Create zip files from the tagged directories common, dtd, test, posix, and tools directories, with the tag (e.g: release-1-3) and post to site for Rick to pick up.
E2a* Done
 rick
 Create a new directory, eg http://unicode.org/Public/cldr/1.9.0/ and populate with the zip files from John.
E2b*
 DONE rick Verify that the links on the release page (eg http://sites.google.com/site/cldr/index/downloads/cldr-1-8) are correct, and Draft is removed from the text.
E2c*
 DONE rick Modify http://sites.google.com/site/cldr/index/downloads so that it includes a new row on the top (Latest:), with the information from the current release (eg http://sites.google.com/site/cldr/index/downloads/cldr-1-9). Might be easiest to do in HTML mode.
E2d*
 DONE rick Change the dtd redirection, so that
  1. http://www.unicode.org/cldr/dtd/(X+1)/points to http://www.unicode.org/cldr/data/dtd/
  2. http://www.unicode.org/cldr/dtd/X/is new. Upload the tagged dtd files there.
  3. edit /home/httpd/htdocs/cldr/dtd/.htaccess and bump the version number to "X+1"
  4. To verify that these are properly accessible, type the new dtd (X+1) URL into a browser, and if you get to the head of CVS, it's correct.
E3* Done
 rick Remove the yellow from UTS#35 draft, and clean up everything for posting. Check into CVS. Then post as final UTS#35 on unicode site
E4* Done
 rick
 Move all X fixed bugs to closed. Steven says this is:
mv -i /home/users/srloomis/locale-bugs/locale_tracking/fixed/* /home/users/srloomis/locale-bugs/locale_tracking/closed/

Similarly, move all "return-survey" items to "returned"
E5* DONE
 mark Update the sidebar for the release, eg:

CLDR 1.8 Schedule: 2009-NN

=>

Latest Release: CLDR 1.8

and gray out the schedule
NOTE: Only the "site owner" can change the sidebar.
E6* DONE
 rick Tell Magda to create a new press page from http://sites.google.com/site/cldr/development/cldr-big-red-switch/draft-press and update the Unicode Home page. The announcement listing should be in New Releases, not Other News.
E7* DONE rick As an announcement, send contents of http://sites.google.com/site/cldr/development/cldr-big-red-switch/draft-press to all the Unicode mailing lists
Cleanup
F1*
 DONE
 emmons Review and handle all X bugs connnected with the final release process
F2*
 DONE rick Move all X open bugs to (X+1) [Only after all reviews are done, & F1 & E4!]
F3
 Done
 rick Disable for now automatic regeneration of the charts and error files
F3a
 DONE rick Change bug email generation to weekly, and update version.








Prepare for next release
G2* ??? Peter Restore locales that were deleted due to lack of data
G3* DONE Chrish Review errata to make sure they match as above:
G4*
 ??? Mark Delete incoming/vetted and incoming/proposed directories. Delete dropbox contents.
G5*
 Done Rick Modify http://unicode.org/draft/reports/tr35/tr35.html to be ready for the next release, and check into CVS.
  • Increase version, change links as necessary so that it is a working draft.






Contributor Message
For each release, we add names to the Unicode CLDR Acknowledgments page:


However, names are not automatically entered there, since some people may not wish to have their names listed. If your name is not there and you would like it to be, please send me your name as it should appear on that page. Your name should be in Latin characters, optionally with names in one or more other scripts in parentheses, such as "Vladimir Weinstein (Владимир Вајнштајн)"


---- how to send this message: currently a crude process ----
1. CLDR SQL query: (with Show All checked)
select email from cldr_users where exists (select * from cldr_vet where cldr_vet.submitter = cldr_users.id)
2. carefully select the 2nd column (I exported the whole web page into a word processor)
3. e-mail that list on BCC: the above message with a subject line of "[CLDR 1.9 Contributor Message]", and a request to please keep the subject line intact.
4. Then, the subject line can be used to filter/locate the contributor requests.