Re: INTENT TO DEPRECATE (taskcluster l10n routing)

[Jet Villegas]

On Sun, Dec 3, 2017 at 05:15 Axel Hecht  wrote:

> Am 01.12.17 um 16:45 schrieb Justin Wood:
> > Hey Everyone,
> >
> > tl;dr if you don't download nightly l10n repacks via taskcluster index
> > routes, this does not affect you.
> >
> > Up until recently you could only find nightly l10n repacks with the
> > following routes:
> >
> > *
> >
> .gecko.v2.{project}.revision.{head_rev}.{build_product}-l10n.{build_name}-{build_type}.{locale}
> > *
> >
> .gecko.v2.{project}.pushdate.{year}.{month}.{day}.{pushdate}.{build_product}-l10n.{build_name}-{build_type}.{locale}
> > *
> >
> {index}.gecko.v2.{project}.latest.{build_product}-l10n.{build_name}-{build_type}.{locale}
> >
> > Recently I have updated the routing to match that of regular Nightlies,
> > specifically one such route is:
> >
> >
> gecko.v2.mozilla-central.nightly.revision.a21f4e2ce5186e2dc9ee411b07e9348866b4ef30.firefox-l10n.linux64-opt
>
> That's followed by locale code, right? I found
>
>
> gecko.v2.mozilla-central.nightly.revision.de1f7a92e8726bdd365d4bbc5e65eaa369fbc20a.firefox-l10n.macosx64-opt.de
>
> > This deprecation is in preparation of actually building l10n repacks on
> > (nearly) every code checkin, rather than just on nightlies.
>
> Does that mean that you're deprecating all but that route, or are there
> more?
>
> > Let me know if there are any questions or concerns.
>
> No concerns, just curiousity. We're not running any tests on localized
> builds at this point, right?
>

I hope we can change that (testing on localized builds) with this proposed
change. We’ve gotten reports that localized builds (and related usage;
e.g., input method editors) cause A11y API activation, which triggers other
bugs for us.



> Axel
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

IMEs can instantiate accessibility (was Re: INTENT TO DEPRECATE (taskcluster l10n routing))

[David Bolter]

On Mon, Dec 4, 2017 at 8:58 AM, Axel Hecht  wrote:

> Am 04.12.17 um 05:42 schrieb Jet Villegas:
>
>>
>> On Sun, Dec 3, 2017 at 05:15 Axel Hecht > l...@mozilla.com>> wrote:
>>
>> Am 01.12.17 um 16:45 schrieb Justin Wood:
>> > Hey Everyone,
>>
>>
[snip]

I hope we can change that (testing on localized builds) with this proposed
>> change. We’ve gotten reports that localized builds (and related usage;
>> e.g., input method editors) cause A11y API activation, which triggers other
>> bugs for us.
>>
>
> My gut reaction is "that shouldn't happen", though, well, no idea what
> IMEs do. Do we have bugs tracking these? I'd love to be on CC on those.
>

It can happen. IMEs often have prediction features and they need to examine
the context under which the input is happening. One example we recently
learned of is a Japanese IME feature ATOK's "insight" which analyzes
focused web content for input prediction and switching dictionaries.

The main side effect is performance.

We need to do two things here:
1. Add more caching to our Windows e10s a11y solution.
2. Do something smart about the different kinds of clients that instantiate
a11y. This will likely be two things: blocking 'a11y' clients who that are
just being ridiculous, and better, copying what Chrome does and instantiate
only 'portions' of our a11y support... think of this as having a
'lightweight' mode, although it may be that we have multiple levers.

Cheers,
D
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: INTENT TO DEPRECATE (taskcluster l10n routing)

[Axel Hecht]

Am 04.12.17 um 05:42 schrieb Jet Villegas:


On Sun, Dec 3, 2017 at 05:15 Axel Hecht > wrote:


Am 01.12.17 um 16:45 schrieb Justin Wood:
> Hey Everyone,
>
> tl;dr if you don't download nightly l10n repacks via taskcluster
index
> routes, this does not affect you.
>
> Up until recently you could only find nightly l10n repacks with the
> following routes:
>
> *
>

.gecko.v2.{project}.revision.{head_rev}.{build_product}-l10n.{build_name}-{build_type}.{locale}
> *
>

.gecko.v2.{project}.pushdate.{year}.{month}.{day}.{pushdate}.{build_product}-l10n.{build_name}-{build_type}.{locale}
> *
>

{index}.gecko.v2.{project}.latest.{build_product}-l10n.{build_name}-{build_type}.{locale}
>
> Recently I have updated the routing to match that of regular
Nightlies,
> specifically one such route is:
>
>

gecko.v2.mozilla-central.nightly.revision.a21f4e2ce5186e2dc9ee411b07e9348866b4ef30.firefox-l10n.linux64-opt

That's followed by locale code, right? I found


gecko.v2.mozilla-central.nightly.revision.de1f7a92e8726bdd365d4bbc5e65eaa369fbc20a.firefox-l10n.macosx64-opt.de



> This deprecation is in preparation of actually building l10n
repacks on
> (nearly) every code checkin, rather than just on nightlies.

Does that mean that you're deprecating all but that route, or are
there
more?

> Let me know if there are any questions or concerns.

No concerns, just curiousity. We're not running any tests on localized
builds at this point, right?


I hope we can change that (testing on localized builds) with this 
proposed change. We’ve gotten reports that localized builds (and 
related usage; e.g., input method editors) cause A11y API activation, 
which triggers other bugs for us.


My gut reaction is "that shouldn't happen", though, well, no idea what 
IMEs do. Do we have bugs tracking these? I'd love to be on CC on those.


As for running tests, we have 100 localizations and 5 platforms, we'll 
need to be pretty conservative on which tests we run so that we don't 
blow up our budget by a factor of 500. Also, many of our tests actually 
hard-code en-US artifacts, like "ensure that the button on this dialog 
says "Save", and thus will fail when run on localized builds. I don't 
have a list, though.


Axel

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: INTENT TO DEPRECATE (taskcluster l10n routing)

[Axel Hecht]

Am 01.12.17 um 16:45 schrieb Justin Wood:

Hey Everyone,

tl;dr if you don't download nightly l10n repacks via taskcluster index
routes, this does not affect you.

Up until recently you could only find nightly l10n repacks with the
following routes:

*
.gecko.v2.{project}.revision.{head_rev}.{build_product}-l10n.{build_name}-{build_type}.{locale}
*
.gecko.v2.{project}.pushdate.{year}.{month}.{day}.{pushdate}.{build_product}-l10n.{build_name}-{build_type}.{locale}
*
{index}.gecko.v2.{project}.latest.{build_product}-l10n.{build_name}-{build_type}.{locale}

Recently I have updated the routing to match that of regular Nightlies,
specifically one such route is:

gecko.v2.mozilla-central.nightly.revision.a21f4e2ce5186e2dc9ee411b07e9348866b4ef30.firefox-l10n.linux64-opt


That's followed by locale code, right? I found

gecko.v2.mozilla-central.nightly.revision.de1f7a92e8726bdd365d4bbc5e65eaa369fbc20a.firefox-l10n.macosx64-opt.de


This deprecation is in preparation of actually building l10n repacks on
(nearly) every code checkin, rather than just on nightlies.


Does that mean that you're deprecating all but that route, or are there 
more?



Let me know if there are any questions or concerns.


No concerns, just curiousity. We're not running any tests on localized 
builds at this point, right?


Axel
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

INTENT TO DEPRECATE (taskcluster l10n routing)

[Justin Wood]

Hey Everyone,

tl;dr if you don't download nightly l10n repacks via taskcluster index
routes, this does not affect you.

Up until recently you could only find nightly l10n repacks with the
following routes:

*
.gecko.v2.{project}.revision.{head_rev}.{build_product}-l10n.{build_name}-{build_type}.{locale}
*
.gecko.v2.{project}.pushdate.{year}.{month}.{day}.{pushdate}.{build_product}-l10n.{build_name}-{build_type}.{locale}
*
{index}.gecko.v2.{project}.latest.{build_product}-l10n.{build_name}-{build_type}.{locale}

Recently I have updated the routing to match that of regular Nightlies,
specifically one such route is:

gecko.v2.mozilla-central.nightly.revision.a21f4e2ce5186e2dc9ee411b07e9348866b4ef30.firefox-l10n.linux64-opt

This deprecation is in preparation of actually building l10n repacks on
(nearly) every code checkin, rather than just on nightlies.

Let me know if there are any questions or concerns.

~Justin Wood (Callek)
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform