LocalisationUpdate was “temporarily” disabled in production half a year ago (Id079776511), presumably as part of Translations on hold until further notice. This was apparently due to a security incident which has since been resolved (Blog Post: translatewiki.net security incident); does that mean we can re-enable the periodic localisation update again?
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T205313 l10nupdate is still using HHVM | |||
| Declined | None | T220481 Reenable l10update in production | |||
| Declined | None | T158360 RFC: Reevaluate LocalisationUpdate extension for WMF | |||
| Open | None | T206694 Determine desired architecture to update localization strings for Wikimedia | |||
| Resolved | dancy | T278019 Why is the LocalisationUpdate extension still enabled in WMF production? |
Event Timeline
Comment Actions
Side note: LocalisationUpdate SAL entries have apparently been sparse since long before then, with the last successful update logged back in 2015. Did something (else) break there?
Comment Actions
There has been runs since 2015: https://tools.wmflabs.org/sal/production?p=0&q=l10nupdate&d=
Reedy manually ran it on 2017-01-23, i suspect the logging format may have changed.
Comment Actions
Re-enabling this will mean having l10n go through the regular backport process happy to work with language folks on this.