BRS item idPrimaryPoolTarget EODStatusTime EstimateDNRPre Req IDOriginal Task #Task DescriptionNotes/ Helpful Links v42Bug/How-To LinksOther Links
New BRS sheetAnnemarie / Mark2022-04-13doneminsDNRS0Proposed: Make a copy of the previous release's tab for next release

Clear SBRS Target EOD, Status; set dates for milestones in BRS
Show new scheduleMark2022-04-13doneminsDNRNew BRS sheetModify versions for the schedule info. After done, correct results should show on
Review new locale requetsMark / DaviddoneminsRNew BRS sheetReview all items in component locale-create and make sure that any new language requests are on track to be added by esub
Schedule finalizationAnnemarie2022-04-20doneminsDNRShow new scheduleS7Add and track agenda item to agree on milestones and dates for the releaseshared schedule
Create SBRS TicketPeter2022-04-06doneminsDNRNew BRS sheetS0.1Create & take SBRS ticket:

the parent ticket, create subtask for different tasks by person
Merge maint branch backPeter, Steven2022-04-11donehoursDNRCreate SBRS TicketE19.5Merge maintenance branch back to main branch
Create directory for new releaseSteven2022-05-09doneminsDNRCreate SBRS TicketCreate a new empty data directory with a readme that says 'IN DEVELOPMENT'
Bump version number and ICU jarsPeter2022-04-13doneminsDNRMerg maint branch back to mainS5- Update CLDR's jars to latest version of ICU.
- Update readme to reflect correct version and status.
- Update GEN_VERSION in to next milestone
- update dtd versions.
- Update versions in pom.xml files See for example
Set Consolecheck to BUILDSteven2022-04-18doneminsDNRBump version number and ICU jarsSet the default Phase for Consolecheck on the server to be BUILD (replace this if we figure out a better mechanism). maven.ymlpr#1922
Tom/StevendoneminsNRS16modify cldr-unittest/build.xml to use -z build instead of -z final_testing on the datacheck target - ST releases only... "run CLDR console check" in maven.yml
Bulk close forum postsTom/Steven2022-04-12doneminsDNRCreate SBRS TicketE18- Auto-close certain forum requests. Log into ST as Admin and choose "Bulk close posts" from the main menu. As of 2021-11-17, the only posts that get auto-closed are "requests" for values matching the final winning value (includes inherited); do after the values for this version are final.
- Add comment to SBRS ticket when complete

Needs to be done before Shakedown
GenCharts1Mark2022-04-27doneminsDNRCreate SBRS TicketRegenerate charts with new version number and check in. Remember to change ToolConstants to add new release, change DEV_VERSION.
Verify BRS ownershipMark / Peter / Annemarie2022-04-20doneminsDNRCreate SBRS TicketS0.2Check owners of BRS items and make sure there are no significant ownership changes due to TC membership changes
Review JIRA teamAnnemarie2022-04-27doneminsNRCreate SBRS TicketS0.05Review JIRA team, GitHub team and CLDR TC group email

- Requires JIRA admin access, and Google Group Manager+ access
- JIRA cldr-tc@ team can be found under Atlassian Administration > Directory tab > Groups > cldr-tc
Update JIRA filtersMark / Annemarie2022-04-27doneminsDNRCreate SBRS TicketS13Update all of the "@CURR" jira filters be editable by group, and to point to the new current milestones ==> v42
Update TZ dataYoshito2022-05-01doneminsDNRCreate SBRS TicketCheck and update TZ data if necessary

This needs to be done before ST opens (ideally as late as possible)
Upgrade serverTom/Steven2022-04-25doneminsDNRCreate SBRS TicketS0.01Upgrade server software to latest versions. Update smoke first to make sure everything works; then the "upgrade-playbook.yml" playbook, but see CLDR-15176
Update ST version number and phase, push to productionTom / Steven2022-04-27donehoursRUpgrade serverS14Update ST and smoketest 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. Edit, set CLDR_PHASE to VETTING_CLOSED --- Question: better to make it SUBMIT on smoketest, for testing?
Tom/Steven2022-04-27doneminsDNRS21Smoketest version numbers updated (CLDR version and Phase)

Merge with 'Update ST version number'?
Update guava & gson libsTom/Steven2022-04-20doneminsDNRCreate SBRS TicketS0.02Update to latest version of guava and gson libs;check to see if we want to update to the latest Java LTS.

May become moot w/depdabot in the future

Discuss at infra meeting week of 4/26
gson: #1900 new way with mvn:
Stub Release PageAnnemarie2022-04-18doneminsDNRCreate SBRS TicketS0.025Create stub release page for next version from template below, so that dev version on works. (We had this as S11 but best to get it done earlier)

Stub Template:
Create a new stub release page for the next release, and update the pages:
Create draft TR35Annemarie/Steven2022-04-25doneminsDNR (rarely D)Merge back maint to mainS0.3Create the draft TR35 for next version and create Github PR so it's open for updates. Header changes, revision number += 1, "Proposed Update", Status=Proposed update...Typical bug subject = Prepare TR35 spec files for CLDR NN proposed update. Include dates, versions, header links, copyright check, and new Mods (yellow) with removed-style on old Mods. (Also run validation and link checks on HTML converted version, when possible.)
TC org language contribution plansPMs2022-05-04donehoursRS25Sharing of Language contribution scope by Company; bring to committee.

Update [CLDR] Locales by company sheet with planned coverage
Organize Java import statementsYoshito2022-04-27doneminsNRS0.04Organize import statements in Java source code (make sure to *not* format merging lines). Do on main branch (and if feasible, on maint branch).

Low priority - okay to go to submission w/out resolving.
Unit test KIs (1st)Mark2022-04-27moothoursNRS0.5Review Known issues in Unit tests (as logged when running the tests).
UNK (only summer cycle)moothoursRS4Make proposal and run by committee for:
Remove / 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. Data Retention Policy
Update Info HubAnnemarie2022-05-04donehoursRS5.2Clean up Information Hub for Linguists
- Remove all sub sections and contents that are not generic.
- Update and modify the generic page to start the new contribution period (or Closed contribution information for the start of a non-contribution release.
- Add information about new data for cycle (if needed)
- Update known issues
Mark to provide a draft guide for person names
Annemarie + Mark (rev)
2022-05-04mootRS28.5Translation landing page: Remove all sub sections and contents that are not generic. Update and modify the generic page to start the new contribution period (or Closed contribution information for start of a non-contribution release.)
Translation landing page is ready with Contribution stage, known issues, new features
Sign-off Info HubAnnemarie2022-05-18donehoursRS6.1Remove ### markers (use for Reviewers) still left in Translation guides. Use blue italicized text for things to highlight to readers. NOTE: clear out highlights for users at Vetting Start, and then after Resolution. Send email after done, asking for review.Need to add:
??mootL??Set Survey Tool to final check to see if there are any errors that would require vetters to resolve in locales that are planned to not open
Check with organizations for coverage changesMark2022-05-16doneminsRS7.5Check with contributing organizations to see if they require any changes to locales.txt, and then make the changes.

- Annemarie to check PR and add any that aren't missing data
Check TC coverage locales.txtPMsmootRS8.2Check coverage for locales, esp new ones (Mark doing ticket for new vendor coverage levels)

Consider combining with: "Check with organizations for coverage changes"
Turn on/off limited submissionSteven2022-04-22doneminsS7.6Set to limited submission / turn off limited submission based on release plans

Make sure CheckCLDR.LIMITED_SUBMISSION is correct for new release on both smoketest and production. Locales and paths if limited.

Formerly 'Set to limited release'
TommootRS13.1Formerly 'Make sure CheckCLDR.LIMITED_SUBMISSION is correct for new release on both smoketest and production.'Make JIRA issue, edit, pull request, ...
Update coverage pathsMark / Peter2022-05-09donehoursS7.7Check coverage, particularly for new structure from last release (eg h0:Hybrid)
Annemarie / Peter(?)2022-05-04mootDNRS8Reminder to all to Review "All current milestone" tickets assigned to them and assess the size (JIRA 'time needed') for the release.
Add emojiMark2022-05-06donehoursDNRS8.1If there are new or updates of Emoji data from ESC that need to come into CLDR, incorporate them.
TC review dsub ticketsAnnemarie / Peter(?)2022-05-16doneDNRS23TC review Dsub tickets (major+)

Jira filter
TommootRS13.2update passwords ... move to end of BRS

Is this moot?

What are the current list of things that require passwords
Tom / Rick2022-05-16in progressRS13.5Check that ST Admin work done in preparation for the upcoming release.


Look at making bounces easier/more streamlined

This is more of a checkpoint to make sure all ST related Admin tasks are done.
mainlly done, except if any new orgs need to be added.
Update script medatdataMark + Markus2022-04-27donehoursRS17File bug and update scriptmetadata for the new Unicode scripts (from beta)
Remove TC status in ST for non-active membersPeter2022-05-11doneminsRS18Reset TC status in SurveyTool for non-regular attendees from TC to Vetter/Manager, before starting next submission

1. Check current list of attendees to TC meetings
2. Remove status of non-attendees
Users who have not responded or acted in 2 cycles
Yoshito / JohnEmootNRS22Do Formatting Java source code; DO NOT JOIN LINES. (Optional)no changes this time. - Yoshito looked at this - we could clean up and format - but a so many codes are affected. I prefer to do it in earlier in development cycle. I will try this after 37.
Set status for non-TCsMark2022-05-04mootRS24Reset TC status for non-regular attendees from TC to Vetter/Manager, before starting next submission

Duplicate of 'Remove TC status in ST'
8-point vote language listPMs2022-06-08doneminsRS26Check list of 'High bar' in coverageLocales.xml

Review the "8-point required for approval" list of locales in coverageLevels.xml and update as appropriate; also the 20 vote items (ST releases only), and the PathHeader. ; bring to committee.

Pending creation '7-vote' level:

Note: This should be done right before submission when it is confirmed the final set of locales

Annemarie to send an email -> use meike's sheet

8 points are not required for locales that only have one TC active

Wait until Microsoft lands; can update before vetting
Update locales.txtAll orgs2022-05-16doneminsRCheck with organizations for coverage changesS27Update Locale.txt as needed (revisited by each company);
Drop Organizations that are no longer active as per policy
GenerateBirthsMark/Steven2022-05-18doneminsRS28GenerateBirths (Review carefully, since annotations have been added)

Should capture last changed made in English

affects English changed count

Already done once; will need to be redone with any English changes for an old thing
Update langs, scripts, curr., zonesYoshito2022-05-09donehoursRS33Update languages/scripts, currencies, timezones - See updating codes. (Just before Desub, so that we get the latest changes)
Pre-shakedown checkpoint2022-05-09donePre-Shakedown checkpoint
Mark/Annemarie2022-05-16doneweeks?S33.1New data tickets are done;
Tom2022-05-09doneminsRS33.4Push to production (checking for gotchas)
Fredrik/Meike2022-05-09doneRS33.6Simple sanity check of the beta on production 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. (Note: Use a Vetter account)
Tom2022-05-12doneminsRS35Move production ST to SUBMIT mode (ST releases only)
Fredrik/Meike2022-05-12doneRS34.5Repeat the sanity check from S33.6 after SUBMIT mode is on.
Start shakedown2022-05-12doneShakedown
All TCmootRS37Start the controlled push to production processPushing to ProductionGithub
Push to production List
All dsub tickets completeAll2022-05-16doneweeksRS37.5Finish all ticket items that affect ST (i.e. Dsub tickets)
Data cleanup passPeter2022-05-16donehoursRun CLDRModify -fp and GenerateDtd with new structure and mods before regular submission
Integrate new CLDR to ICUPeter2022-05-25donedaysRIntegrate new CLDR structure to ICU
Shakedown completeMeike / Annemarie / Fredrik2022-05-18donehoursRS38Shakedown done and all essential bug fixes have been fixed or documented under known issues
Annemarie / sign-off from PMs needed2022-05-16doneminsRS38.2Draft Submission start message.

The Survey Tool is now open for General Submission for data to be included in CLDR version XX.

Add teaser about focus areas.

Please start by visiting the information hub: 
look at previous messages and capture template here.
Update latest ICU tagged releasePeter2022-05-26doneminsRShakedown has startedS29.7Update to latest tagged release of ICU (eg ICU 66.1 preview release tag instead of master)

Should this be merged with a different ticket?
Push to productionTom2022-05-18doneminsRShakedown completePush to production (checking for gotchas)
Send submission start message to vettersTom / Annemarie / Rick2022-05-18doneminsRS38.7Send submission start message to vetters (admin access: Rick, Mark, Steve, Tom, Peter)
Generate births (pre-submission)Mark2022-06-01doneminsRAll dsub tickets completeRegenerate births if there are any new English changes

Should create a GitHub action for this; Mark to file tickets
Start Submissionall2022-05-18doneRS39Submission starts!!
Submission blog postMark2022-06-01doneminsRS39.5Compose & send blog post, based on Submission message (cut material only relevant to active vetters)Is this moot? Haven't done a blog post since v36 for start of Submission. Discuss this 6/19 with Mark
Remove old daily vote backupsTom2022-05-25doneminsRD49Remove old daily vote backups as per policy: "Ongoing release keep: daily.
Last release keep: start submission, start vetting, end vetting, + weekly.
Previous releases, keep: start, end."
Not as automated as it could be
Mark2022-06-19mootRS50Run HTML clean up on TR35 — TidyDiscuss on 6/19
Review access list for Azure credentialsTomminsRS51Review access list for Azure credentialsCLDR Server Internals: be skipped; not sure this should be in the BRS; need to discuss the process.
Mark2022-05-18doneminsRS10Regenerate charts for submission; follow Generating Charts.
2022-06-15donehoursReview and prioritize dvet tickets, and make sure they get started
doneminsstart 1 week before vettingAdd agenda item to look at flagged items until end of resolution.
Change Smoketest to vettingdoneUpdate smoke test to vetting mode
Change ST to vettingdoneUpdate production ST to vetting mode
Update CLDR site to announce vettingdoneUpdate info hub with messaging about moving into vetting mode & send announcement
Vetting startsall2022-06-22doneminsVetting starts!!!
Change smoketest to resolutionTom / Steven (Tom)2022-07-11doneminsRUpdate smoke test to resolution mode
Change ST to resolutionTom / Steven (Tom)2022-07-06doneminsRA00Change ST to Dispute Resolution; in, CLDR_PHASE=DISPUTED and
CLDR_HEADER=Open for Dispute Resolution
Update CLDR site to announce resolution2022-07-11doneminsUpdate info hub with messaging about moving into resolution mode & send announcement
Resolution startsall2022-07-11doneminsResolution starts!!!
all2022-07-18donehoursRA01Dispute Resolution - fix as many errors as possible in ST until 0 errors - or until determined that all remaining errors are known/documented or easier to fix in XML than ST.
all; begin at Vetting start2022-07-11doneminsRA01.2Copy into spreadsheet, distribute among TC. Take care of all flagged items.[note from annemarie] - we haven't been doing this, should we start again?
Move to VXML2022-07-18doneResolution ends and data is moved to XML
Change ST to read-only modeTom / Steven2022-07-20doneminsRA03Change ST to read-only ; modify .github/workflows/maven.yml to use -z final_testing instead of -z build on the datacheck target (This will change the behavior of the automated build. )
Make branchSteven / Tom2022-07-19doneRA03A04Download from ST into brs/vXXvxml (must be done after ST has been changed to Read-only mode (item A03) to avoid losing data!!)owners to cleanup
Notify TC of read-only mode stage changeTom / Annemarie2022-07-20doneminsRA03A03.5Send email to cldr-core2 when ST moves to Read-only mode.
(Removed ICU as this milestone is not of interest to ICU)
Fix all errors in vXMLTom / Mark / Peter7/21/2022donehoursRA04A04.4Run ConsoleCheckCLDR on brs/vXXvxml, distribute errors to be fixed; (with options: -e -z final_testing - work the error count down to 0Check on this to see if necessary
Merge vXML into mainSteven/ Peter2022-07-21doneminsRAfter errors are fixed, merge brs/vXXvxml into main, use merge-commit (special handling!)
Main updated from ST2022-07-22done
Data freeze reminderAnnemarie2022-07-25doneminsDNRA04.5Jira tickets Reminder to Assignees: CLDR TCs first review/send reminders on open tickets for current milestone (data items need to be completed by the 8th)Issues for current release not including docs/spec/BRS:

All issues for current release:
Mark2022-07-20doneminsDNRA04.6A04.8Regenerate charts (add churn to regular chart generation)Mark to flesh-out description
Annemarie2022-08-01doneminsDNRA04.85Reminder! Send note to everyone to look at tickets requiring any manual data changes (that affect ICU!!) that need to go in before we attempt to freeze the main data.query for items in vNN that are not done, and review and track
Update Known issues for current releaseSteven / Tom2022-07-25doneminsNRA04.9Make sure Known Issues from previous release are being taken care of. (for download page); carry over others into new release page

Link to edit site:
Identify languages to move languages from seed to commonAnnemarie / Peter2022-07-27doneminsRA04.8A05[Semi-automated now, from charts]
1. Produce recommendations for which locales have enough data to move from seed to common or vice versa. Bring to committee to make decision, and implement.
2. After item above, generate list of possible new locales for ICU and distribute to <>, for discussion/approval before ICU integration.
Pretty much everything that meets the criteria to be in common (#1) except for 2-3 legacy exceptions (that would probably not meet those citeria): cu, io, ...
recommend by email; look at coverage chart for candidates. Recently we have been using >95% of basic coverage and >70% (or 75%?) of core coverage
Update pluralsMark / Steven2022-08-01donehoursDNRA05.1Update the plurals as per the link:
alpha0 ICU integerationPeter2022-07-27donedaysDNRA05.2Preliminary ICU integration (alpha0)
CLDR/ICU calendar
Sanity check chartsAnnemarie / Mark / Fredrik2022-08-03in progressDNRA04.8A05.3Review delta charts for sanity/data issues, and add info to release note page or bring recommendations to TC:

1. Review in the TC meeting: and
2. Review a locale for anything looking odd, eg
3. Review Churn chart (new from v38) and bring issues to the TC