Hey Everyone, I want to share with you all the big picture view of where I see L10n (L20n too) Automation over the course of this next year.
Last week in Hawaii, myself, Pike, gps, and mshal met and discussed the overall plan and what we need from each other, we discussed what my rough plan is as well, and since we all seemed to be on the same page as "this makes sense" and some of "That's where I'd like it too". I figured now is as good a time as any to share it. * First, get all L10n repacks (currently based on nightly code) into Taskcluster, so being based on in-tree code, and inspectable. -- Includes cross-compiled-on-linux OSX repacks. * Reduce mozharness code for l10n greatly, to simplify what we are staring at, (remove buildbot bits once we no longer need buildbot for l10n) * Create on-checkin jobs for l10n repacks, that operate on a small set of (stable) locales and are based on the opt varients of the platforms. * Lastly, move away from mozharness entirely, in favor of a simplified approach using `./mach` machinery in tree -- This could include, or be future-work to allow artifact build l10n. We'll keep it all testable on try, and with-in-tree hacking (documented) allowed to extend the list of locales used for various bits too. A Blue Sky approach that may or may not happen in 2017 from my seat: * (discoverable somehow) Taskcluster jobs based on any checkin to the various l10n repos -- These jobs would be a repack of whatever gecko repo(s) they apply to. -- Would produce xpi's, but not (necessarily) full binaries. -- Could include a job (or some jobs) that produces screenshots of various parts of the UX, similar to some of the work you may have seen around Firefox for iOS localized screenshots. Most of this work does not yet have bugs on file, but I wanted to share it early. Thank You, ~Justin Wood (Callek) _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
