Hey Everyone,
I have recently decided to take ownership of Localization from a
Release Engineering perspective. Specifically what this means is that
I'll own most bustages in the process as it relates to our
infrastructure, as well as work on systemic improvements and overall
long-standing desires in the system.
I have recently taken Nick's initial work for L10n on Try (c.f.
footnote 1) And created a similar Taskcluster L10n-on-try job, (c.f.
footnote 2); as part of the Taskcluster work I have helped round out
using the in-tree compare-locales instead of the external repo {older}
copy.
I initially had a draft going on where I hoped to head next, however I
think getting your input will help me formulate concrete
thoughts/plans better.
Two things I do know for sure:
* Make L10n always depend on an en-US build that is based on the
changeset we're using. (This allows us to more-easily [re]-trigger
l10n on older nightly changesets, and can improve the coverage
potential with l10n-on-try)
* Make Android L10n testable on try.
What I am wondering is what sort of use-cases do you want/need from
releng with regard to l10n. What cool thing have you always hoped
Release Engineering could provide that we have never had the resources
for.
What use-cases do you have for L10n builds provided by us currently?
What things could we do that would make your lives easier with regard
to l10n.
(Feel free to think outside the box, or even propose things like "it'd
be awesome if I could click on any UI and do a live translation", or
"It'd be awesome if I could select any string, and see how it would
look live in Firefox on each platform" -- while both of those are cool
ideas, they are outside the realm of what I envision being done
anytime soon, but ideas *you* have can be simpler than you think, or
at least help me to architect around improvements we want, rather than
improvements I *think* we want).
By all means this is an open invitation to tell me both what has been
wrong with Relengs L10n support and what you want from Relengs L10n
Support.
(Due to the nature of the system and lots of technical debt I don't
promise any timelines yet, and will hesitantly promise any actual
features)
Thank You,
~Justin Wood (Callek)
footnotes:
1 - https://wiki.mozilla.org/ReleaseEngineering/TryServer#Desktop_l10n_jobs
2 - force-buildable with `-p linux-l10n,linux64-l10n` or with `-p
linux,linux64` if you touch one of the known-affected files for l10n.
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
