QA/Execution/Meetings/2007-12-20: Difference between revisions

no edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
<small>[[QA/Execution/Meetings/2007-12-06|« previous mtg]] | [[QA/Execution/Meetings|index]] | [[QA/Execution/Meetings/2007-12-20|next mtg »]]</small>
<small>[[QA/Execution/Meetings/2007-12-13|« previous mtg]] | [[QA/Execution/Meetings|index]] | [[QA/Execution/Meetings/2007-12-27|next mtg »]]</small>


== Meeting Agenda: ==
== Meeting Agenda: ==
Line 9: Line 9:
* Fx3 update (tchung)
* Fx3 update (tchung)
** [http://wiki.mozilla.org/QA/Firefox3/TestPlan#Test_Areas Testplans]complete them by Q4
** [http://wiki.mozilla.org/QA/Firefox3/TestPlan#Test_Areas Testplans]complete them by Q4
*** '''UPDATE''' - timr and tchung has a good grasp on the status of completion.  will roll up a summary in the next firefox meeting.
*** '''UPDATE''' - '''timr''' and '''tchung''' gathered verbal status on testplan.  will roll up a summary in the next firefox meeting.
*** '''martijn''' will add a testplan for Gecko test cases.


** [http://wiki.mozilla.org/QA/Firefox3/TestPlan#Review_Feedback Feedback Rollup page]
** [http://wiki.mozilla.org/QA/Firefox3/TestPlan#Review_Feedback Feedback Rollup page]
** Ownership needed to develop test cases for Breakpad [marcia]
** Ownership needed to develop test cases for Breakpad [marcia]
***Email sent regarding the issue but no feedback was received. Currently we should ensure before we ship that breakpad is not only installed but that it fires and that data ends up on the server. The Win Vista issue surfaced very late in the game for Beta 2, and as a result we will not have any crash feedback for that OS until someone figures out what is going on in that bug.
***Email sent regarding the issue but no feedback was received. Currently we should ensure before we ship that breakpad is not only installed but that it fires and that data ends up on the server. The Win Vista issue surfaced very late in the game for Beta 2, and as a result we will not have any crash feedback for that OS until someone figures out what is going on in that bug.
**** '''DISCUSSION''' - sam to add testcases on ways to include tests for breakpad into litmus.  Will disable these tests from community.
**** '''DISCUSSION''' - '''sam''' to add testcases on ways to include tests for breakpad into litmus.  Will disable these tests from community.
**** Sam will own keeping breakpad up and running


* TB 1.5.0.14 update (al)
* TB 1.5.0.14 update (al)
Line 27: Line 27:
** '''UPDATE''' - Completed restructured 3.0 areas.  eg. collaborated security tests
** '''UPDATE''' - Completed restructured 3.0 areas.  eg. collaborated security tests
** cleaned up FFTs and BFTS
** cleaned up FFTs and BFTS
** todo: keep up your area clean.  If you have a massive change (eg. string for Places Organizer), ask coop to change it in the backend.
** '''litmus admins''': keep up your feature area clean.  If you have a massive change (eg. string for Places Organizer), ask coop to change it in the backend.


* Discuss bugzilla component for litmus?  
* Discuss bugzilla component for litmus?  
Line 37: Line 37:


* Testday this week on trunk (tomcat)
* Testday this week on trunk (tomcat)
** '''UPDATE''' - '''jay''' followed up with top testday members, and pinged them
* Vacations.  (Update the Mozilla calendar)
* Vacations.  (Update the Mozilla calendar)
-----
-----
* Other topics?
* Other topics?
Confirmed users
6,361

edits