Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

comm-beta Bug 835002 very late breaking string change

14 views
Skip to first unread message

Ian Neal

unread,
Feb 13, 2013, 5:31:40 PM2/13/13
to
First of all apologies to all our hard working translators.

Bug 835002 - Add back Growl support for TB19/20 and SM2.16/2.17 landed
on comm-beta yesterday. It was considered to be worth landing even if
there couldn't be l10n coverage.

http://hg.mozilla.org/releases/comm-beta/rev/c32f17244f9a

This will affect SM more than TB as there will be a SM release off the
current comm-beta.

Again, on behalf of the comm-* developers, we apologise for the lateness
of this change.

Regards,

Ian

Ian Neal

unread,
Feb 13, 2013, 7:43:01 PM2/13/13
to
Just as a follow-up, it has also just landed on comm-aurora too.

Regards,

Ian

Iacopo Benesperi

unread,
Feb 14, 2013, 5:53:30 AM2/14/13
to
Ian Neal ha scritto:
> Bug 835002 - Add back Growl support for TB19/20 and SM2.16/2.17 landed
> on comm-beta yesterday. It was considered to be worth landing even if
> there couldn't be l10n coverage.

I have translated the string, submitted the commit and did the sign-off.
Do you think you can accept it and build with the new string?

Iacopo

Justin Wood (Callek)

unread,
Feb 15, 2013, 7:32:13 PM2/15/13
to
Our last beta [releasing today] went to build right after that commit
landed, so will be missing your l10n (similar to all the other l10n
fixup signoffs I got)

And *normally* we don't accept l10n changes after the last beta goes to
build, but due to this late-change. I accepted all of the requests and
they will be present in our 2.16 final, expected to GO to build later
this evening (release on tuesday)

--
~Justin Wood (Callek)

0 new messages