# Localisation strings missing: pre-release checklist

Source: https://releasefailures.com/incidents/localisation-strings-missing/
Content version: 1.0.0
Verified on: 2026-10-21
Licence: CC BY 4.0

Definition: A release ships with missing or untranslated strings in one locale.
- [ ] 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. (test class: Configuration and environment tests)
- [ ] 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. (test class: Configuration and environment tests)
- [ ] PR-03 Launch the release candidate with the language set to pt-PT and fail the run on any console error about a missing .ftl file. (test class: End-to-end tests)
- [ ] PR-04 Open 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. (test class: End-to-end tests)
- [ ] PR-05 Open the OpenPGP Key Manager menu and the import and export tool in each shipped locale and confirm their labels differ from en-US. (test class: End-to-end tests)
- [ ] PR-06 Confirm the pt-PT build of the release uses the pinned localisation changesets of the release, not the latest localisation repository. (test class: Configuration and environment tests)
- [ ] PR-07 Add 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. (test class: Synthetic monitoring)