Summit2008/Sessions/Proposals/Localizing Firefox 3: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 2: Line 2:




A review of Firefox 3 with discussion on what happened, what could have been done better, what we'll do differently going forward.  Focus of the discussion is on how can we can improve and scale better across all our products in more languages including emerging markets like Asia, Africa, etc.
A review of Firefox 3 with discussion on what happened, what could have been done better, what we'll do differently going forward.   


== Development ==
== Development and Release Management ==
 
axel
 
* development and translation dashboard
* communication of schedules and freeze dates
 
== Release Management ==


axel/mic/pacal
axel/mic/pacal


* opt-in process for betas, RCs and Final
* recap sprint through the releases
* webservices
* websites


== QA Testing ==
== QA Testing ==
Line 23: Line 18:
* improving the organization of testing activities and reporting testing results.   
* improving the organization of testing activities and reporting testing results.   


* brief analysis of our [firefox 3 process | http://groups.google.com/group/mozilla.dev.l10n/browse_thread/thread/a6310fe801fd4f0f/8b6e33c1b76eb87e?lnk=gst&q=new+testing+requirements#8b6e33c1b76eb87e]   
* brief analysis of our [http://groups.google.com/group/mozilla.dev.l10n/browse_thread/thread/a6310fe801fd4f0f/8b6e33c1b76eb87e?lnk=gst&q=new+testing+requirements#8b6e33c1b76eb87e firefox 3 process]   


* where are the weak areas and pain points for localization teams?
* where are the weak areas and pain points for localization teams?
Line 29: Line 24:
* how can we get wider coverage on features and platforms?
* how can we get wider coverage on features and platforms?


*  brainstorming and discussion on where testing work is organized across locale teams and how test cases are run and reported.  brainstorming on improvements we need to QMO, QAC, Litmus, to help l10n teams, and engage more international testers.
== Discussion ==


== Tools and Process ==
* release announcements, opt-in process
* brainstorming and discussion on where testing work is organized across locale teams and how test cases are run and reported.  brainstorming on improvements we need to QMO, QAC, Litmus, to help l10n teams, and engage more international testers.
*  discussion and exploration of tools and process that each localization team is using and how they can be leveraged and shared.
*  discussion and exploration of tools and process that each localization team is using and how they can be leveraged and shared.
** pt-PT testing tool demonstration?  
** pt-PT testing tool demonstration?  
** project on Spanish portal which has some low end easy testing questions,
** project on Spanish portal which has some low end easy testing questions,

Revision as of 07:53, 26 July 2008

Introduction

A review of Firefox 3 with discussion on what happened, what could have been done better, what we'll do differently going forward.

Development and Release Management

axel/mic/pacal

  • recap sprint through the releases
  • webservices
  • websites

QA Testing

chofmann/timr

  • improving the organization of testing activities and reporting testing results.
  • where are the weak areas and pain points for localization teams?
  • how can we get wider coverage on features and platforms?

Discussion

  • release announcements, opt-in process
  • brainstorming and discussion on where testing work is organized across locale teams and how test cases are run and reported. brainstorming on improvements we need to QMO, QAC, Litmus, to help l10n teams, and engage more international testers.
  • discussion and exploration of tools and process that each localization team is using and how they can be leveraged and shared.
    • pt-PT testing tool demonstration?
    • project on Spanish portal which has some low end easy testing questions,