QA/Execution/Meetings/2007-10-04: Difference between revisions

← Older edit

QA/Execution/Meetings/2007-10-04 (view source)

Revision as of 19:58, 15 November 2007

686 bytes added , 15 November 2007

no edit summary

Samuelsidler

1,457

edits

@@ Line 1: / Line 1: @@
-[http://wiki.mozilla.org/QAE << Back To QAE page]
+<small>[[QA/Execution/Meetings/2007-09-27|« previous mtg]] | [[QA/Execution/Meetings|index]] | [[QA/Execution/Meetings/2007-10-11|next mtg »]]</small>
 == Meeting Agenda: ==
@@ Line 33: / Line 33: @@
 *** '''DISCUSSION''' - UI is not ready.  still awaiting a lot of changes and updates.  stability is okay, but concerns evolve around performance issues.  (eg. launching bookmarks in browser, large history stored)  Mac issues still bad.  widgets, focus issues.  download manager is okay.  Unified toolbar bugs on mac theme may have problematic regression issues.  Builds are still pretty crashy (more bugs filed within the last week).
-** Need QA owner for [http://wiki.mozilla.org/Firefox3/Product_Requirements_Document#Search Search] and [http://wiki.mozilla.org/Firefox3/Product_Requirements_Document#Tabbed_browsing Tabbed Browsing]feature (tchung)
+* Seeking QA owner for [http://wiki.mozilla.org/Firefox3/Product_Requirements_Document#Search Search] and [http://wiki.mozilla.org/Firefox3/Product_Requirements_Document#Tabbed_browsing Tabbed Browsing]feature (tchung)
-*** '''RESOLVED''' - Tabbed Browsing (marcia), Search feature (tomcat).  Thanks guys.
+** '''RESOLVED''' - Tabbed Browsing (marcia), Search feature (tomcat).  Thanks guys.
 * Continued discussion on testing profiles.  (timr)
@@ Line 44: / Line 44: @@
 * Load balancing Litmus test cases [Litmus Triage team]
-** '''DISCUSSION''' - better way to get litmus ? bugs to be marked in litmus and verified.  some people have bigger areas in litmus than others.  how can we better balance the workload?
+** '''DISCUSSION''' - better way to get litmus ? bugs to be marked in litmus and verified.  For now, feature owners arent complaining too much.  Will revisit later.
 * Who owns the l10n cases in Litmus? [Litmus Triage team]
 ** '''DISCUSSION''' - someone can create the test suite and organize the list of test cases.  If its feature based, each owner of that feature should be helping out with adding test cases for their areas to the test suite. But what about the areas no one owns?  (eg. printing, rss, preferences, etc..)
-** Who will be the litmus l10n test suite caretaker?   We may have to drop this if we cant find an owner.
+** Who will be the litmus l10n test suite caretaker?   One idea is to push this back on the localizer owner.  We can be the faciliator and available for questions, but we dont have the time or bandwidth to cover this.
+** Continued to discuss this in weekly l10n meeting (timr)
 * Keeping up with getting test cases in Litmus when bugs are VERIFIED in bugzilla [Litmus Triage Team]
+** '''RESOLVED''' - important for each person to keep their eye on their feature first.  Make sure in-litmus? becomes + if assigned to them.  Marcia to crack whip if its not happening.
+** reminder to run the litmus test case after you create it, so the result becomes a last point of reference in record.
 * Thoughts on eggplant and public virtual machine?  Based off email from last week... (tracy)
+** '''DISCUSSION''' - timr checked with bhearsum on a solution for public vm.  tracy to take conversation offline with ben.
 * Other topics?