Re: Future of L10n Releng Automation -- Open for Requests/Use-Cases

2016-07-18 Thread Gregory Szorc
On Mon, Jul 18, 2016 at 6:48 AM, Justin Wood wrote: > 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

Re: Upcoming changes to in-tree generation of test tasks

2016-07-18 Thread Dustin Mitchell
This change will, if luck is with me, be landing today. Dustin 2016-07-01 17:37 GMT-05:00 Dustin Mitchell : > Hi folks -- > > Just to raise awareness that there's a major refactor coming down the > pike. If you've wrestled with the YAML files in taskcluster/ci/legacy > (nee testing/taskcluster)

Re: Future of L10n Releng Automation -- Open for Requests/Use-Cases

2016-07-18 Thread Nicholas Alexander
Hi Callek, On Mon, Jul 18, 2016 at 6:48 AM, Justin Wood wrote: > Hey Everyone, > > I have recently decided to take ownership of Localization from a > Release Engineering perspective. \o/ I'm glad to see clear ownership of this underloved area. > Specifically what this means is that > I'll

Re: Future of L10n Releng Automation -- Open for Requests/Use-Cases

2016-07-18 Thread Axel Hecht
Hi Justin, the two you listed sound great, thanks. I have a few other things: * l10n (on a small subset) for all jobs on automation (try, integration, central) * A well-defined sequence of scopes for taskcluster/buildbot, mozharness, mach, make. * Unification of artifact builds and l10n repa

Future of L10n Releng Automation -- Open for Requests/Use-Cases

2016-07-18 Thread Justin Wood
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 desire