QA/QA Services/Meetings/2011-03-23

From MozillaWiki
Jump to: navigation, search

« previous mtg | QA Services Home | next mtg »

QA Services Team Meeting

  • March 23, 2011
  • Attendees: ashughes, mevans, marcia, whimboo

Upcoming Bug/Testdays

Discussion Items

Project Status

CrashKill [tomcat/marcia]

  • Marcia
    • Investigating new crash issues for Firefox 4
      • There are likely to be some new flash issues appearing and we should watch out for them.
    • Several new bugs filed yesterday
  • Tomcat
    • watching plugins (esp. flash issues)
    • keeping an close eye on crash stats
    • crashhunters (automation) is hammering on data

Accessibility Status Update [marco]

  • Initial Firefox 4 feedback indicates some problems on Windows XP with two commercial screen readers. The reason why this was not brought to our attention earlier is probably due to high Windows 7 adoption among early adopters. One of the bugs is bug 644084, and we're investigating other issues. On Windows 7, and the small percentage on Vista, things are OK.
  • Queue is building up for m-c landings after the tree reopens.
  • We are also planning on some stuff to land for the first 4.0.x release. Some approved blockers there.

Community Building/Events (ideas and progress) [marcia/tomcat/ashughes]

QA Videos [marcia]

  • No update on video work at this time. When Rainer returns there will be more progress on this.

QMO [abillings]

TCM [aakashd]

  • Going to feature complete tomorrow, 3/24
  • Working on wireframes and workflow for .3 release

Roundtable

Meeting Notes/Action Items

  • Action Items
    • Matt to send out notes re: the Director's Meeting
    • Add brainstorming session to possible All Hands Schedule
    • marcia to Contact person from the last test day regarding prizes
  • Ideas
    • Concept of an alert box for things that need QA-all feedback?
    • Keep QA Services intact until Work Week - Then evaluate going forward
    • Parallel releases -> Can we have a group that is identified with Firefox 5
      • Ownership over the release
      • Expert for this particular feature
      • Tighter scope for what a particular release is
      • Community Teams ?
      • Assigned to a feature - as opposed to a branch?
      • Experimentation how we can attract more folks to check it out?
        • Virtual classrooms - video conferencing
        • Open spaces operational by next quarter?
        • P2P University
          • Teaching a class on Selenium
    • Virtual Classes on:
      • Automation Frameworks
      • MozMill
      • Testing these marketing sites - is that a possibility? Barriers are the surprise element.