Hi Callek,
On Mon, Jul 18, 2016 at 6:48 AM, Justin Wood <jw...@mozilla.com> 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 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)
>
It's my opinion that Releng needs to figure out the "task B depends on
build A depends on pre-step Z" flow. When I last checked, ~3 months ago,
we had one case (test B depends on build A) and it was not handled
generally. Defining and documenting this (if it hasn't already happened!)
unlocks the value in TC.
> * Make Android L10n testable on try.
>
Axel brings it up below, but making l10n repacks work like artifact builds
would go a long way to improving turn-around times. It's not clear this is
in Releng's court -- I think the build system needs to change to make this
happen.
Nick
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
