Localisation strings missing: pre-release and first 30 minutes checklists

A release ships with missing or untranslated strings in one locale.

The pre-release checklist maps each item to a test class from the incident page. The first-30-minutes checklist covers detection, containment, the rollback decision and customer communication.

7 pre-release items · 7 first-30-minutes items · verified 2026-10-21

Pre-release checklist

PR-01At the release gate, compare the string keys of each shipped locale with en-US and fail on any new key with no translation. config
PR-02Compare the list of .ftl files the release candidate loads in en-US with the files present in each locale and fail on any missing file. config
PR-03Launch the release candidate with the language set to pt-PT and fail the run on any console error about a missing .ftl file. e2e
PR-04Open the room list with the language set to Russian and confirm the Unreads, People, Rooms, Sort and Activity labels do not match their en-US text. e2e
PR-05Open the OpenPGP Key Manager menu and the import and export tool in each shipped locale and confirm their labels differ from en-US. e2e
PR-06Confirm the pt-PT build of the release uses the pinned localisation changesets of the release, not the latest localisation repository. config
PR-07Add a post-deploy synthetic check per shipped locale that loads one screen with new strings and fails when its labels equal the en-US text. synthetic

First 30 minutes

FM-01Reproduce the report by switching the interface language to the affected locale and listing every label that appears in English.
FM-02Open the console of the affected locale build and record any error about a missing .ftl file.
FM-03Compare the localisation files of the affected locale with en-US for the shipped version to find missing files or late strings.
FM-04Decide between a point release with the missing files and waiting for the next scheduled release, based on how many screens fall back to English.
FM-05Roll back only if the fallback hides a required action from users of that locale, because the English text still works.
FM-06Reply on the issue tracker to the users of the affected locale with the release that will carry the translations.
FM-07Before shipping the fix, confirm a build with the missing files present shows the translated strings in the affected locale.

Download the checklist

Pre-release checklist (Markdown)1.5 KB · v1.0.0
First 30 minutes checklist (Markdown)1.2 KB · v1.0.0

Only in this checklist

Every test class in this checklist also appears in at least one sibling checklist in the group; the item texts differ: At the release gate, compare the string keys of each shipped locale with en-US and fail on any new key with no translation.

Questions

What should be checked before a release to prevent Localisation strings missing?

7 pre-release items, PR-01 to PR-07. PR-01: At the release gate, compare the string keys of each shipped locale with en-US and fail on any new key with no translation.

Is there a rollback plan for Localisation strings missing?

The first-30-minutes checklist has 7 items. FM-01: Reproduce the report by switching the interface language to the affected locale and listing every label that appears in English.

What should a team do in the first 30 minutes after Localisation strings missing is detected?

The first-30-minutes checklist has 7 items. FM-01: Reproduce the report by switching the interface language to the affected locale and listing every label that appears in English.

Which configuration checks apply to Localisation strings missing?

PR-01: At the release gate, compare the string keys of each shipped locale with en-US and fail on any new key with no translation. PR-02: Compare the list of .ftl files the release candidate loads in en-US with the files present in each locale and fail on any missing file. PR-06: Confirm the pt-PT build of the release uses the pinned localisation changesets of the release, not the latest localisation repository.

Is a Localisation strings missing checklist still needed if deployment is automated?

Yes. Automation runs the steps; the checklist names what the tests must cover: configuration and environment tests, end-to-end tests and synthetic monitoring.

Which pipeline stages does the Localisation strings missing checklist cover?

The pre-release items map to the pre-deploy and post-deploy stages.