User:Tsk/Docs/Todo list: Difference between revisions

No edit summary
No edit summary
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
* Think about perf testing
* Think about perf testing
* Get into [https://wiki.mozilla.org/Thunderbird:Testing https://wiki.mozilla.org/Thunderbird:Testing]
* <s>Get into and follow the [https://wiki.mozilla.org/BMO_Reorg_Phase_2  bugzilla reorganization ]</s>
* Write the plan for QA
* Write the plan for QA
* Grow QA community:
* Grow QA community:
** engage OpenSolaris community
** engage Linux distro community (Ubuntu,Fedora)
** engage Linux distro community (OpenSuse, Ubuntu my primary targets)
** engage Calendar community
** engage Calendar community
** engage Corporation using TB ? (Windows users)
** engage Corporation using TB ? (Windows users)
** engage usenet/email newsgroups (General more than he english ones)
** engage usenet/email newsgroups (General more than he english ones)
** Start discussion and act on that.
* Figure out security
* Figure out tooling
* Figure out tooling
** look into litmus and how much [https://litmus.mozilla.org/show_test.cgi?searchType=by_category&product_id=3&branch_id=&testgroup_id=&subgroup_id= coverage] we have.
** look into litmus and how much [https://litmus.mozilla.org/show_test.cgi?searchType=by_category&product_id=3&branch_id=&testgroup_id=&subgroup_id= coverage] we have.
** look for where to file bug, ENH bug in bugzilla, if not there file.  
** look for where to file bug, ENH bug in bugzilla, if not there file.
** learn to query and graph Bugzilla.  
* add website to QA plans.
* add website to QA plans.
* tell the world.
* {{bug|2903}}
* organize litmus day.
* il devrait y avoir un triager qui checke tous les patchs sans review et les reassigne
* topcrash issues.
 
=== 3.0b3 ===
 
* search/filter
* OpenSolaris builds (?)
* Communicate better what build to use for Testing
* Builds for Ubuntu -
* FFT
* Bug day
* Figure out new features

Latest revision as of 14:13, 25 February 2009

  • Think about perf testing
  • Write the plan for QA
  • Grow QA community:
    • engage Linux distro community (Ubuntu,Fedora)
    • engage Calendar community
    • engage Corporation using TB ? (Windows users)
    • engage usenet/email newsgroups (General more than he english ones)
  • Figure out tooling
    • look into litmus and how much coverage we have.
    • look for where to file bug, ENH bug in bugzilla, if not there file.
    • learn to query and graph Bugzilla.
  • add website to QA plans.
  • bug 2903
  • organize litmus day.
  • il devrait y avoir un triager qui checke tous les patchs sans review et les reassigne
  • topcrash issues.

3.0b3

  • search/filter
  • OpenSolaris builds (?)
  • Communicate better what build to use for Testing
  • Builds for Ubuntu -
  • FFT
  • Bug day
  • Figure out new features