Opting in to RC1 - new testing requirements

1 view
Skip to first unread message

Mic

unread,
Apr 3, 2008, 5:53:28 PM4/3/08
to
Hey everyone

We are changing the opt-in process for this final release to include a
testing review. We have asked for this in the past but this is the
first time we'll be requiring that you complete testing before you opt
in. The
reason is we want to ensure the standard of quality we've all come to
expect. For new locales this is especially important so please lean on
l10n-drivers and other localizers to help. So, as we get closer to
final release of Firefox 3 all localization teams need to be ready to
start ramping down engineering and translation work, and start ramping
up the amount of testing, watching feedback channels, and also focus
on any remaining critical bug fixing and translation work.

To help support you all l10n-drivers will be working this weekend and
will be hanging out in l10n channel. Any of us can help so feel free
to ping: pascalc, mic, chofmann, Pike (Axel) and from QA: tchung,
tomcat,
timr.

Here's what we will be expecting before you opt-in:
1 conduct litmus test: <https://litmus.mozilla.org> or <https://
litmus.mozilla.org/run_tests.cgi?test_run_id=16> look for "Firefox
3.0 l10n Localizer Test Run". For instructions on how
to run these tests go to <http://quality.mozilla.org/node/71>.
2 Reporting your litmus results - you can pass/fail the tests from
the Firefox 3.0 l10n Localizer Test Run, and QA will run a query on
your results. For those that run tests in other areas (like Fx3.0
bfts, ffts), we
would have to know the testgroup, date, and locale used, and QA can
query results. To get this information please open a tracking bug and
comment there or email l10n-d...@mozilla.org.

3 Gain community or beta tester reviews - send us any links to
communities you are monitoring for feedback, for example we've seen
this community in China, <http://hall.sociz.com/index.php?showforum=7>

Here's data that we have about your locale, can you tell us what you
think about it:
* number of untranslated strings <http://l10n.mozilla.org/dashboard/>,
in particular <http://l10n.mozilla.org/dashboard/unchanged.html>
** are the strings that are not translated highly visible in product?
** are there strings that need to be translated before RC1?
** if so, do you think you can you get it done in time?

Here is a minimum list of dialog boxes that are important and highly
visible that must be in good shape for RC1, in addition to those
already covered by the litmus test run:
* help box for updates
* SUMO integration, from preferences, too
* Add-ons manager, suggested add-ons should work

If you would like to run a testing event to get the work done feel
free to email se...@mozilla.com for ideas and potential sponsorship
help. You can also contact me (m...@mozilla.com) directly for feedback,
concerns, etc.

Thank you,
Mic

Tomer Cohen - mozilla.org.il

unread,
Apr 3, 2008, 6:35:27 PM4/3/08
to
The RTL mac theme is almost ready, and we would like to merge it into
the tree and than get some community feedback. Can it be done for RC1?
This is a major issue, since three locales are unable to produce mac
builds before it lands.


RTL locales - Please follow us in bug 364536.

Axel Hecht

unread,
Apr 3, 2008, 7:19:49 PM4/3/08
to

beltzner volunteered Ryan Flint for review, but if anybody has skills in
writing and debugging skins, feel free to jump in and help.

Axel

Mic

unread,
Apr 4, 2008, 2:33:41 PM4/4/08
to
thanks to Cedric I now realize I did not provide a deadline :)

This work should be done for RC1, the current deadline for RC1 is
supposed to be Tuesday April 8. I'm watching http://wiki.mozilla.org/Releases
and beltzner for the latest and will post if anything is new

Please make your tests etc and opt in *before* (or by) then. Please do
not hesitate to ping any of l10n-drivers if you need or want help!

Francesco Lodolo

unread,
Apr 6, 2008, 5:08:09 AM4/6/08
to Mic, dev-...@lists.mozilla.org
>
> * SUMO integration, from preferences, too
>
How can we test this point? Help is still pointing to an English
placeholder.

Francesco.

Ville Pohjanheimo

unread,
Apr 6, 2008, 6:03:23 AM4/6/08
to
04/04/08 00:53, Mic kirjoitti:

>
> Here is a minimum list of dialog boxes that are important and highly
> visible that must be in good shape for RC1, in addition to those
> already covered by the litmus test run:
> * help box for updates
> * SUMO integration, from preferences, too
> * Add-ons manager, suggested add-ons should work
>

Um, I'm confused. What is meant by "help box for updates"? Can I somehow
spawn this box so I can check it? And are localizers now also
responsible for making sure AMO suggested extensions work ... or is the
third point just about "Get Extension" dialog functionality?

Also, does SUMO integration mean that the Help-buttons work and link or
something more. As Francesco notes in another message in this thread,
SUMO currently has a placeholder page for en-US too...


-ville/mozilla.fi

Axel Hecht

unread,
Apr 6, 2008, 8:45:11 AM4/6/08
to
Ville Pohjanheimo wrote:
> 04/04/08 00:53, Mic kirjoitti:
>>
>> Here is a minimum list of dialog boxes that are important and highly
>> visible that must be in good shape for RC1, in addition to those
>> already covered by the litmus test run:
>> * help box for updates
>> * SUMO integration, from preferences, too
>> * Add-ons manager, suggested add-ons should work
>>
>
> Um, I'm confused. What is meant by "help box for updates"? Can I somehow
> spawn this box so I can check it? And are localizers now also
> responsible for making sure AMO suggested extensions work ... or is the
> third point just about "Get Extension" dialog functionality?

"Help box for updates" is a cryptic way of saying "check for updates in
the help menu".

For the add-ons manager, you should test that the "Get Extension" pane
works. Which it doesn't for localizations with transcribed product
names, so much I can tell.

> Also, does SUMO integration mean that the Help-buttons work and link or
> something more. As Francesco notes in another message in this thread,
> SUMO currently has a placeholder page for en-US too...

That sumo still links to en-US placeholders is darn unfortunate. Is
there a bug on that?

Axel

pascal

unread,
Apr 6, 2008, 9:10:29 AM4/6/08
to Mozilla l10n, Mic
Francesco Lodolo a écrit :

Type about:config and look for network.http.redirection-limit , set it to 0

This will disable the http redirect.

Click on the help menu item and you will no longer be redirected to the
placeholder. The URL should contain your locale and operating system. In
a nightly build I get :
http://support.mozilla.com/1/firefox/3.0pre/Linux/fr/firefox-help

Pascal

Francesco Lodolo

unread,
Apr 6, 2008, 9:18:09 AM4/6/08
to Mozilla l10n, Mic
pascal ha scritto:

> Click on the help menu item and you will no longer be redirected to the
> placeholder. The URL should contain your locale and operating system. In
> a nightly build I get :
> http://support.mozilla.com/1/firefox/3.0pre/Linux/fr/firefox-help
Yep, I see the redirect error page but the URL seems good

Mac OS X: http://support.mozilla.com/1/firefox/3.0pre/Darwin/it/firefox-help
Win XP: http://support.mozilla.com/1/firefox/3.0pre/WINNT/it/firefox-help

Francesco.

Francesco Lodolo

unread,
Apr 6, 2008, 9:39:14 AM4/6/08
to Axel Hecht, dev-...@lists.mozilla.org, michal...@gmail.com, djst.m...@gmail.com
Axel Hecht:

> That sumo still links to en-US placeholders is darn unfortunate. Is
> there a bug on that?
The only bug that I can find is the one who put on the static page redirect
https://bugzilla.mozilla.org/show_bug.cgi?id=425372
(or https://bugzilla.mozilla.org/show_bug.cgi?id=425377 )

I can't find any bugs about removing those rules from .htaccess and I
don't know if SUMO is ready to take the load (last time it wasn't).

Maybe we should ping also David Tenser or Chris Ilias about this topic
(adding David to cc of this mail).

Francesco.

Cédric Corazza

unread,
Apr 6, 2008, 2:53:03 PM4/6/08
to

Francesco Lodolo

unread,
Apr 6, 2008, 2:58:51 PM4/6/08
to Mic, dev-...@lists.mozilla.org
Italian is asking to opt-in for RC1.

*Litmus tests*
Litmus tests (I run personally tests for Mac OS X, Linux and Windows Vista).
http://tinyurl.com/4eu565

Also: since beta2 I've been using nightly versions on Mac OS X and
Windows (both Vista and Windows XP) for everyday web browsing, and the
person who's updating Italian version of SUMO has been using nightly
builds on Linux in the last weeks.

*Community test*
Since Firefox 3.0b2 we've been using our forum to test, fix and improve
Italian localization
http://forum.mozillaitalia.org/index.php?topic=30515.0

*Untranslated strings*
I checked the untranslated strings and I've localized a couple of
strings in the installer; all remaining strings are correct (Italian
word is the same of the English one).

Francesco.

Ville Pohjanheimo

unread,
Apr 6, 2008, 4:44:36 PM4/6/08
to

Finnish (fi) opting in for RC1.

Litmus test completed successfully for Linux, Windows XP/Vista.

Some little testing chatter intermixed with other messages on our forums
at http://www.mozilla.fi/keskustelu/. Untranslated strings ok (generic,
same as en-us, low visibility), other raised issues ok too.

-ville/mozilla.fi

Alexandru Szasz

unread,
Apr 7, 2008, 1:20:21 AM4/7/08
to dev-...@lists.mozilla.org
Romanian (ro) is opting in for RC1.

The litmus tests ran on Windows XP, Linux and Windows Vista, but I
couldn't run the help window test since the online help doesn't seem
to work just yet.

The untranslated strings are either the same in Romanian or they
describe security/internet terms.

We don't have a forum just yet, just the old mozilla-ro group on
google: http://groups.google.com/mozilla-ro

--
Alexandru Szasz

Julen

unread,
Apr 7, 2008, 5:50:24 AM4/7/08
to dev-...@lists.mozilla.org
On Thu, Apr 3, 2008 at 11:53 PM, Mic <michal...@gmail.com> wrote:
>
> 2 Reporting your litmus results - you can pass/fail the tests from
> the Firefox 3.0 l10n Localizer Test Run, and QA will run a query on
> your results. For those that run tests in other areas (like Fx3.0
> bfts, ffts), we
> would have to know the testgroup, date, and locale used, and QA can
> query results. To get this information please open a tracking bug and
> comment there or email l10n-d...@mozilla.org.

We have found that two accesskeys are equal so one "eats" the other.
Just reporting the test as Failed and fixing the key on CVS is enough?

Julen.

Alexander L. Slovesnik

unread,
Apr 7, 2008, 2:34:14 PM4/7/08
to

Mad Maks

unread,
Apr 7, 2008, 2:38:07 PM4/7/08
to

Axel Hecht

unread,
Apr 7, 2008, 3:57:39 PM4/7/08
to

Yes.

Axel

Filip Miletic

unread,
Apr 7, 2008, 4:54:21 PM4/7/08
to

Ayman Hourieh

unread,
Apr 7, 2008, 5:51:15 PM4/7/08
to

Axel Hecht

unread,
Apr 8, 2008, 9:34:40 AM4/8/08
to

Do you have testers on Mac?

Axel

Axel Hecht

unread,
Apr 8, 2008, 9:40:37 AM4/8/08
to

Do you have testers for Mac and Windows?

Axel

Axel Hecht

unread,
Apr 8, 2008, 9:42:55 AM4/8/08
to

I see tons of tests submitted on Windows and Linux :-) , do you have
testers on Mac, though?

Axel

Axel Hecht

unread,
Apr 8, 2008, 9:44:25 AM4/8/08
to

Hi,

I see windows testing, how is it looking on Linux? And I know it's
looking bad on Mac, right?

Axel

Mad Maks

unread,
Apr 8, 2008, 1:55:02 PM4/8/08
to
Axel Hecht schreef:
nope not any more :-(, do you now anyone? I am trying to get a old mac
here to do some testing.

Axel Hecht

unread,
Apr 8, 2008, 5:36:58 PM4/8/08
to

I'm taking notes. I won't be able to organize real testing for you, but
I should be able to get you at least some data.

Axel

Wim

unread,
Apr 9, 2008, 8:28:38 AM4/9/08
to dev-...@lists.mozilla.org
2008/4/8, Axel Hecht <l1...@mozilla.com>:


It would be nice if you could include the frisian version also, because I
cannot seem to find a mac user until now.
Isn't there a way to run a Mac on vmware or something?

Wim

Axel Hecht

unread,
Apr 9, 2008, 9:54:31 AM4/9/08
to Alexandru Szasz

Alexandru, doing some mac testing (more on that separately) I found that
the Romanian localization on Mac doesn't quit on apple-Q, but apple-E.

Is that standard for Romanian Mac software, or is that a bug?

Axel

Axel Hecht

unread,
Apr 9, 2008, 10:00:38 AM4/9/08
to Wim

Sadly, OSX only runs on mac hardware, IIRC, you're violating the license
if you do anything else.

Included in test (see other thread), but:

There command key for quit is broken. It's set to apple-o, but that's
open, too.

I guess it should be apple-q, like for all mac apps.

Axel

willyaranda

unread,
Apr 9, 2008, 10:47:46 AM4/9/08
to
Hi!

es-ES is opting in to RC1, we have done some test in Linux, Windows
and Mac, and all things we have saw has been fixed.

Regards, Guillermo.

Ayman Hourieh

unread,
Apr 9, 2008, 6:31:15 PM4/9/08
to
On Apr 8, 2:44 pm, Axel Hecht <l...@mozilla.com> wrote:
> Ayman Hourieh wrote:
> > Hello,
>
> > Arabic (ar) is opting for RC 1.
>
> > Litmus:
> >https://litmus.mozilla.org/search_results.cgi?order_by_created=&order...

>
> > Community:
> >http://lists.arabeyes.org/mailman/listinfo/doc
>
> > Untranslated strings:
> > Most of them are strings that cannot be translated.
>
> > Thanks,
>
> > -Ayman
>
> Hi,
>
> I see windows testing, how is it looking on Linux? And I know it's
> looking bad on Mac, right?
>
> Axel

I did the Litmus tests for Linux and found things to be good. Link is
in the real "opting in to RC1" thread.

I haven't had the chance to test the work done on the Mac theme yet...

-Ayman

Axel Hecht

unread,
Apr 9, 2008, 7:49:41 PM4/9/08
to

There's http://l10n.mozilla.org/~axel/screens/ar/mac.html to scare
children. Though nothing looks quite as bad as the main toolbar, really.

Axel

Toni Hermoso Pulido

unread,
Apr 9, 2008, 8:12:47 PM4/9/08
to dev-...@lists.mozilla.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ca opting for RC1

https://litmus.mozilla.org/search_results.cgi?order_by_created=&order_by_testcase_id=&order_by_product=&order_by_platform=&order_by_branch=&order_by_locale=&timespan=&summary=&product=&platform=&branch=&locale=ca&limit=100

Daily usage of users in different platforms.

Unchanged strings are those which are the same as in en-US.

Some window sizes still need to be corrected in Mac, though. Hope this
might be mostly finished this morning (UTC+2) if l10n tree is not closed
yet.

Cheers!

- --
Toni Hermoso Pulido
http://www.cau.cat
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH/Vt/3O471rZ7Q9wRAtTRAJ9z5wmto3GXA8hiLVtzwi0kJ8anqQCeOXCC
PV84sdl3sRqEQD0UcTyTQoE=
=Yj1y
-----END PGP SIGNATURE-----

Khaled Hosny

unread,
Apr 10, 2008, 3:16:20 AM4/10/08
to Axel Hecht, dev-...@lists.mozilla.org

I can ask some Arabic mac users for testing FF3, but what is needed
exactly?

--
Khaled Hosny

signature.asc

Axel Hecht

unread,
Apr 10, 2008, 7:12:23 AM4/10/08
to
Toni Hermoso Pulido wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> ca opting for RC1
>
> https://litmus.mozilla.org/search_results.cgi?order_by_created=&order_by_testcase_id=&order_by_product=&order_by_platform=&order_by_branch=&order_by_locale=&timespan=&summary=&product=&platform=&branch=&locale=ca&limit=100
>
> Daily usage of users in different platforms.
>
> Unchanged strings are those which are the same as in en-US.
>
> Some window sizes still need to be corrected in Mac, though. Hope this
> might be mostly finished this morning (UTC+2) if l10n tree is not closed
> yet.
>

That's still cool, tree closes at 23:59 PST today, Thursday.

Axel

Axel Hecht

unread,
Apr 10, 2008, 7:20:23 AM4/10/08
to

Right now, I guess the Mac is unusable from what I see. I'm not sure
what to ask users beyond "can you stand the toolbar as is?". And I
wouldn't be surprised to hear a "no".

Axel

Toni Hermoso Pulido

unread,
Apr 10, 2008, 9:36:11 AM4/10/08
to Axel Hecht, dev-...@lists.mozilla.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

En/na Axel Hecht ha escrit:

I don't know whether it's a visual effect or an error in capture, but in
my testing I see the entire window (new profile, not tried any resizing):
http://l10n.mozilla.org/~axel/screens/ca/prefs_paneAdvanced_encryptionPanel_viewCertificatesButton_webCerts_mac.png
but in this image that do not appear so...

- --
Toni Hermoso Pulido
http://www.cau.cat
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH/hfK3O471rZ7Q9wRAqGYAJ4/DVLmKcUWS1HCSX2EJajdhfXcQgCeLXH5
ClZa/djrqsHbeJ3aCGf3YmI=
=Q4pE
-----END PGP SIGNATURE-----

Axel Hecht

unread,
Apr 10, 2008, 9:41:48 AM4/10/08
to
Toni Hermoso Pulido wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> En/na Axel Hecht ha escrit:
>> Toni Hermoso Pulido wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> ca opting for RC1
>>>
>>> https://litmus.mozilla.org/search_results.cgi?order_by_created=&order_by_testcase_id=&order_by_product=&order_by_platform=&order_by_branch=&order_by_locale=&timespan=&summary=&product=&platform=&branch=&locale=ca&limit=100
>>>
>>> Daily usage of users in different platforms.
>>>
>>> Unchanged strings are those which are the same as in en-US.
>>>
>>> Some window sizes still need to be corrected in Mac, though. Hope this
>>> might be mostly finished this morning (UTC+2) if l10n tree is not closed
>>> yet.
>>>
>> That's still cool, tree closes at 23:59 PST today, Thursday.
>>
>
> I don't know whether it's a visual effect or an error in capture, but in
> my testing I see the entire window (new profile, not tried any resizing):
> http://l10n.mozilla.org/~axel/screens/ca/prefs_paneAdvanced_encryptionPanel_viewCertificatesButton_webCerts_mac.png
> but in this image that do not appear so...
>

The certManager window is statically sized, but persists the set size.
So it will likely look cropped on a new profile, but looks ok on yours
as you have resized the dialog in your previous life.

As you can't fix it, the croppage is OK.

Axel

Khaled Hosny

unread,
Apr 10, 2008, 9:48:56 AM4/10/08
to Axel Hecht, dev-...@lists.mozilla.org

I see, we don't need testing then, we already know it is broken.

--
Khaled Hosny

signature.asc

danishka

unread,
May 28, 2008, 2:51:21 PM5/28/08
to m...@mozilla.com
The Sinhala (si) locale opts-in. We made the Litmus tests for GNU/
Linux.

https://litmus.mozilla.org/advanced_search.cgi?test_run=&product=7&branch=19&testgroup=89&subgroup=883&testcase=&platform=&opsys=&locale=si-LK&result_status=&start_date=&timespan=&end_date=Now&search_field1=&match_criteria1=contains_all&search_value1=&search_field2=&match_criteria2=contains_all&search_value2=&search_field3=&match_criteria3=contains_all&search_value3=&search_field4=&match_criteria4=contains_all&search_value4=&sort_field1=&sort_order1=ASC&sort_field2=&sort_order2=ASC&sort_field3=&sort_order3=ASC&sort_field4=&sort_order4=ASC&limit=15&automated=all&withbugs=all&email=&trusted_only=all&vetted_only=all&valid_only=1

Mic wrote:
> Hey everyone
>
> We are changing the opt-in process for this final release to include a
> testing review. We have asked for this in the past but this is the
> first time we'll be requiring that you complete testing before you opt
> in. The
> reason is we want to ensure the standard of quality we've all come to
> expect. For new locales this is especially important so please lean on
> l10n-drivers and other localizers to help. So, as we get closer to
> final release of Firefox 3 all localization teams need to be ready to
> start ramping down engineering and translation work, and start ramping
> up the amount of testing, watching feedback channels, and also focus
> on any remaining critical bug fixing and translation work.
>
> To help support you all l10n-drivers will be working this weekend and
> will be hanging out in l10n channel. Any of us can help so feel free
> to ping: pascalc, mic, chofmann, Pike (Axel) and from QA: tchung,
> tomcat,
> timr.
>
> Here's what we will be expecting before you opt-in:
> 1 conduct litmus test: <https://litmus.mozilla.org> or <https://
> litmus.mozilla.org/run_tests.cgi?test_run_id=16> look for "Firefox
> 3.0 l10n Localizer Test Run". For instructions on how
> to run these tests go to <http://quality.mozilla.org/node/71>.


> 2 Reporting your litmus results - you can pass/fail the tests from
> the Firefox 3.0 l10n Localizer Test Run, and QA will run a query on
> your results. For those that run tests in other areas (like Fx3.0
> bfts, ffts), we
> would have to know the testgroup, date, and locale used, and QA can
> query results. To get this information please open a tracking bug and
> comment there or email l10n-d...@mozilla.org.
>

> 3 Gain community or beta tester reviews - send us any links to
> communities you are monitoring for feedback, for example we've seen
> this community in China, <http://hall.sociz.com/index.php?showforum=7>
>
> Here's data that we have about your locale, can you tell us what you
> think about it:
> * number of untranslated strings <http://l10n.mozilla.org/dashboard/>,
> in particular <http://l10n.mozilla.org/dashboard/unchanged.html>
> ** are the strings that are not translated highly visible in product?
> ** are there strings that need to be translated before RC1?
> ** if so, do you think you can you get it done in time?
>
> Here is a minimum list of dialog boxes that are important and highly
> visible that must be in good shape for RC1, in addition to those
> already covered by the litmus test run:
> * help box for updates
> * SUMO integration, from preferences, too
> * Add-ons manager, suggested add-ons should work
>
> If you would like to run a testing event to get the work done feel
> free to email se...@mozilla.com for ideas and potential sponsorship
> help. You can also contact me (m...@mozilla.com) directly for feedback,
> concerns, etc.
>
> Thank you,
> Mic

Reply all
Reply to author
Forward
0 new messages