[Mozilla] Fwd: Opting in to RC1 - new testing requirements

[Julen]

Gabon !!

Firefox 3 B5 argitaratu da eta konturatu aurretik RC1 gainean dugu.
RC1en barruan sartzeko baldintzak "gogortu" egin dituzte eta, besteak
beste, beharrezkoa da litmus testak egitea. Horretarako
Windows/Mac/Linux sistematan egin behar ditugu testak.

Animatzen?

Julen.

---------- Forwarded message ----------
From: Mic <michalmberman en gmail.com>
Date: Thu, Apr 3, 2008 at 11:53 PM
Subject: Opting in to RC1 - new testing requirements
To: dev-l10n en lists.mozilla.org


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-drivers en 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 sethb en mozilla.com for ideas and potential sponsorship
 help. You can also contact me (mic en mozilla.com) directly for feedback,
 concerns, etc.

 Thank you,
 Mic
 _______________________________________________
 dev-l10n mailing list
 dev-l10n en lists.mozilla.org
 https://lists.mozilla.org/listinfo/dev-l10n