Closed Bug 1497565 Opened 6 years ago Closed 6 years ago

Rename locales to locales-src to avoid accidentally exporting l10n-exposed strings

Categories

(Firefox :: New Tab Page, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
Firefox 64
Iteration:
65.1 - Nov 2
Tracking Status
firefox64 --- fixed

People

(Reporter: Mardak, Assigned: Mardak)

References

Details

Attachments

(1 file)

In bug 1496246, we accidentally did a normal export / buildmc that copies over our browser/locales/…/newtab.properties file that then gets exposed to localization. In the past, I've just manually excluded the string file (while keeping the browser/components/newtab/{,prerendered/}locales/… changes), but I failed to catch it in the review process.

The string changes don't need to be exported because l10n-central already has a unified view of strings across central, beta, etc., so just having the string in mozilla-central is sufficient.

However, the string changes also lead to undesired l10n signoffs as noted in bug 1496246 comment 20.
Iteration: --- → 65.1 (Nov 2)
Priority: -- → P3
In our 5-whys, we realized that mercurial hook was requiring l10n= on uplifts for both the browser/locales and browser/components/newtab/locales directories when the latter one was rubber-stamped but the former should actually be prevented.

https://github.com/mozilla/version-control-tools/blob/master/hghooks/mozhghooks/prevent_string_changes.py#L41

We can avoid this by renaming our locales directory to something else: locales-src

With this fix, we won't need l10n= and sherrifs should know to not add it for activity stream uplifts.
Assignee: nobody → edilee
Priority: P3 → P1
Summary: Don't export l10n-exposed strings for mozilla-beta uplifts → Rename locales to locales-src to avoid accidentally exporting l10n-exposed strings
Here's the locales/en-US files under browser/components/newtab:

browser/components/newtab/locales/en-US/strings.properties
browser/components/newtab/prerendered/locales/en-US/activity-stream-noscripts.html
browser/components/newtab/prerendered/locales/en-US/activity-stream-prerendered-noscripts.html
browser/components/newtab/prerendered/locales/en-US/activity-stream-strings.js
browser/components/newtab/prerendered/locales/en-US/activity-stream.html
browser/components/newtab/prerendered/locales/en-US/activity-stream-prerendered.html

So only the first line should be caught by mercurial hook although we should be careful that we don't end up exporting files that end in '.dtd', '.ini', '.properties'

We could rename prerendered/locales/en-US to something else.. e.g., locales-prerendered (NB: prerendered-locales/en-US would still match RegEx(locales/en-US/) ;), but we can skip that for now…
Commit pushed to master at https://github.com/mozilla/activity-stream

https://github.com/mozilla/activity-stream/commit/0fb3f8c2671c37356716880b27389d81354b1ab1
Fix Bug 1497565 - Rename locales to locales-src to avoid accidentally exporting l10n-exposed strings (#4506)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Blocks: 1499886
The changes here just prevents accidentally triggering hghook for undesired files while bug 1499901 is actually preventing uplift changes to a desired file (browser/locales/en-US/chrome/browser/activity-stream/newtab.properties).
Blocks: 1457223
See Also: → as-build-beta-script
Component: Activity Streams: Newtab → New Tab Page
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: