Two Aurora Uplifts in support of ESR17

[Alex Keybl]

I'd like to send a quick email about a couple of bugs with l10n impact that we're looking to uplift to Aurora in the next week. Both are motivated by the fact that the next ESR version is FF17.

Click To Play Blocklist (desktop):
738698 – [meta] Users should have the ability to activate plugins on demand
754472 – click-to-play: implement multiple plugin door hanger ui

Android Updater (mobile):
786380 – Write new Android service-based updater

The motivation for bringing CTP forward into FF17 is that we want to be able to protect our ESR users in the same way we protect our mainline users over the next year. We're also considering supporting a mobile ESR release in the near future, and we don't want to wait till ESR24 to make that possible (as an updater would be a pre-requisite).

We understand that breaking string freeze is very undesirable and causes l10n churn, and we hope you agree that these two instances warrant making that difficult decision. Thanks for your understanding and continued support.

-Alex

[Jørgen Rasmussen]

Den 18-09-2012 22:37 skrev Alex Keybl:
> I'd like to send a quick email about a couple of bugs with l10n impact that we're looking to uplift to Aurora in the next week. Both are motivated by the fact that the next ESR version is FF17.
>
> Click To Play Blocklist (desktop):
> 738698 – [meta] Users should have the ability to activate plugins on demand
> 754472 – click-to-play: implement multiple plugin door hanger ui
>
> Android Updater (mobile):
> 786380 – Write new Android service-based updater

Is it possible to get a couple of screen shots of the Updater
notifications? Viewing them in the right context will help me localizing
the strings.

>
> The motivation for bringing CTP forward into FF17 is that we want to be able to protect our ESR users in the same way we protect our mainline users over the next year. We're also considering supporting a mobile ESR release in the near future, and we don't want to wait till ESR24 to make that possible (as an updater would be a pre-requisite).
>
> We understand that breaking string freeze is very undesirable and causes l10n churn, and we hope you agree that these two instances warrant making that difficult decision. Thanks for your understanding and continued support.
>
> -Alex
>

--
Regards JR

[Axel Hecht]

We had two patches landing for this one yesterday.

Alex, Sheila, are we done with the uplifts?

Axel

[Axel Hecht]

We had two patches landing for this one yesterday.

Alex, Sheila, are we done with the uplifts?

Axel

On 18.09.12 22:37, Alex Keybl wrote:

[Alex Keybl]

> Alex, Sheila, are we done with the uplifts?

Yep - these are the only two uplifts that are planned for CTP blocklisting with l10n impact.

-Alex

[flod]

I won't whine about the fact that breaking string freeze in Aurora less
than a week before merge day (and for ESR too) is painfully wrong, but at
least for the future you shouldn't change a string and keep the same entity
name
http://hg.mozilla.org/mozilla-central/diff/644aac25b7ab/browser/locales/en-US/chrome/browser/browser.properties#l1.13

Francesco

[Alex Keybl]

> for the future you shouldn't change a string and keep the same entity name
> http://hg.mozilla.org/mozilla-central/diff/644aac25b7ab/browser/locales/en-US/chrome/browser/browser.properties#l1.13

Good to know - who's going to take point to make sure that developers know this in the future? I trust you'll file a bug if this is very disruptive and needs to be fixed for FF17/18.

-Alex

[flod]

Il 03/10/12 22:27, Alex Keybl ha scritto:

> Good to know - who's going to take point to make sure that developers
> know this in the future? I trust you'll file a bug if this is very
> disruptive and needs to be fixed for FF17/18.
>

At this point in the cycle I would leave Aurora's repository alone (Axel?).

This document was written some months ago, but the "rule" has always
been there
https://developer.mozilla.org/en-US/docs/Making_String_Changes [*]

Unfortunately it seems that a lot of people are not aware of the right
behavior lately. This is the last example:
https://bugzilla.mozilla.org/show_bug.cgi?id=797036#c6

If that's ok for developers (it's not, but let's say it is), I think
that at least reviewers should be a lot more careful, in particular when
changing string days before merge (the mess goes into Aurora and then
you'll have to break string freeze to fix it).

Francesco

[Jonathan Kew]

On 4/10/12 05:58, flod wrote:
> Il 03/10/12 22:27, Alex Keybl ha scritto:
>> Good to know - who's going to take point to make sure that developers
>> know this in the future? I trust you'll file a bug if this is very
>> disruptive and needs to be fixed for FF17/18.
>>
> At this point in the cycle I would leave Aurora's repository alone (Axel?).
>
> This document was written some months ago, but the "rule" has always
> been there
> https://developer.mozilla.org/en-US/docs/Making_String_Changes [*]
>
> Unfortunately it seems that a lot of people are not aware of the right
> behavior lately. This is the last example:
> https://bugzilla.mozilla.org/show_bug.cgi?id=797036#c6

Looking at the patch there and the string changes it made, ISTM that the
proper action would be to back out that bug and post a corrected patch
for re-review with appropriate changes to entity names.

Maybe someone closer to that area of the code/product should take
another look, and decide how to proceed...

JK

>
> If that's ok for developers (it's not, but let's say it is), I think
> that at least reviewers should be a lot more careful, in particular when
> changing string days before merge (the mess goes into Aurora and then
> you'll have to break string freeze to fix it).
>
> Francesco
>
>

> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>

[Axel Hecht]

I think we shouldn't bother fixing that for 17. At this point, those
localizations that pick up on the changes also follow the discussion
here, and know what they're doing, and interrupting that work hurts more
than it helps.

We should get a fix for 18, though.

Axel

[Axel Hecht]

On 03.10.12 22:27, Alex Keybl wrote: