Find a HA home for the pieces of l10n that block releases. Ideally cache the data required in an git/hg repo and only pull from there. Touch base again on this: 2017-07-28.

Touch base on this as discussed during post-mortem - it's been an hectic week so haven't had too much time to deal with this. Will follow-up next week with :jlorenzo to discuss about this.

(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #1) > Touch base on this as discussed during post-mortem - it's been an hectic > week so haven't had too much time to deal with this. Will follow-up next > week with :jlorenzo to discuss about this. Still no progress on this yet. Shipping 55.0 and related took most of my time. Will have a look at this as soon as my plate gets emptier.

Not actively working on this but I reckon this is done now. @jlorenzo: can we close this?

Thanks for digging this issue up. AFAIK, this is not done, we still rely on http://l10n.mozilla-community.org/ only. However bug 1385401 made the strings not blocking the release anymore. Also, we haven't had any issue with l10n.m-c.o for the past year. I'd suggest to close the current bug and reopen it if we want to actually replicate the server content.

(In reply to Johan Lorenzo [:jlorenzo] from comment #4) > Thanks for digging this issue up. AFAIK, this is not done, we still rely on > http://l10n.mozilla-community.org/ only. However bug 1385401 made the > strings not blocking the release anymore. > > Also, we haven't had any issue with l10n.m-c.o for the past year. > > I'd suggest to close the current bug and reopen it if we want to actually > replicate the server content. Sounds good,thanks!