Open Bug 1359033 Opened 3 years ago Updated 3 years ago
[notifications] Fix sending new string notifications
There are a few cases when we send new strings notifications but we shouldn't, and vice versa. We do not send notifications, but we should: - If new symmetric (bilingual) file is enabled for a locale (e.g. in Mozilla.org), we should notify contibutors of that localization about new strings. Currently we don't send any notifications when such event occurs. We do send notifications, but we should not: - If we not only add new strings, but also pretranslate them in repository using existing translations (e.g. on merge to Firefox Beta or when files are moved in the l10n repo on merge day), we shouldn't notify project contributors about them. - If source strings are different depending on locale (e.g. Mozilla.org or Engagement), we should send notifications only to contibutors of locales for which the new strings were added. Currently we notify all project contributors, even if new strings are only enabled for a handful of locales.
Summary: Fix sending new string notifications → [notifications] Fix sending new string notifications
You need to log in before you can comment on or make changes to this bug.