CLDR: Big Red Switch
The BRS (Big Red Switch) is the checklist of tasks that need to be completed in order to release the next version of CLDR.
For members of the CLDR TC: Spreadsheet View
The checklist can be filtered to see open tasks by going to Data > Change view and selecting the ‘Skip/Done/Moot’ filter.
TODO: List all major types of tasks with their definitions and link to pages with descriptions.
Jira filters for release management and issue triage
Ticket Triage
- @New, by date - All untriaged issues sorted by date created.
- @New, by fix version - All untriaged issues sorted by fix version when available.
- @New + Agenda, by date
- @Agenda - All issues tagged for TC discussion.
- CLDR + ICU helpwanted - Tickets tagged as ‘Help Wanted’ by the CLDR or ICU Technical Committees.
Ticket Reviewing
- @Pending Reviews - All CLDR tickets currently in review.
- @My Reviews - CLDR tickets in review assigned to oneself.
Release tracking
Downloads page
- latest-tickets - All issues with status ‘Fixed’ in the latest version (the most recently released version of CLDR).
- dev-tickets - All issues with status ‘Fixed’ in the dev (the CLDR version currently under development).
General filters
- @CURR CLDR (vXX) - All issues targeting the current release regardless of status.
- @CLDR Known Issues - Current list of known issues.
- @CURR mine — v48, current phase+ - CLDR tickets in review assigned to oneself for the current and future phases of the release in development.
SBRS filters
- @labels=vetter-data - All issues that are expected to impact vetters during data submission.
- @SBRS My tickets Current Milestone (vXX) - CLDR SBRS tickets for the dev version assigned to oneself.
CLDR alpha filters
- @CURR icu-data - Open tickets which impact data used by ICU, and therefore may be disruptive to ICU if changed too late.
- @alpha-critical - Open tickets which must be done in preparation for public alpha.
- @CURR - my open tickets not in brs, charts, docs-spec, site - Open tickets excluding docs, spec, charts and BRS tasks for current fix version.
- @CURR - open tickets not in brs, charts, site, docs-spec, test-data - Open tickets excluding brs, charts, site, docs-spec, test-data for current fix version.
CLDR beta filters
- @beta-critical - Open tickets which must be done in preparation for data beta or public beta.
- @CURR docs-spec Accepted - All open CLDR spec tickets for the version currently in development.
Contributor Message
For each release, we add names to the Unicode CLDR Acknowledgments page:
http://cldr.unicode.org/index/acknowledgments.
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 ----
- 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)
- e-mail that list on BCC: the above message with a subject line of “[CLDR X.Y Contributor Message]”, and a request to please keep the subject line intact.
- Then, the subject line can be used to filter/locate the contributor requests.