QA/Execution/Meetings/2009-02-11: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Meetings
Jump to navigation Jump to search
Line 28: Line 28:
*** QA test signoff - +5 days  
*** QA test signoff - +5 days  
** Tracking [http://spreadsheets.google.com/ccc?key=pnyCb4cp33faqpi709iEhcA&hl=en Status page]  
** Tracking [http://spreadsheets.google.com/ccc?key=pnyCb4cp33faqpi709iEhcA&hl=en Status page]  
*** Update testing progress percentages
*** Update your testing progress percentages


* 3.0 -> 3.1b3 major update trial run (abillings)
* 3.0 -> 3.1b3 major update trial run (abillings)

Revision as of 17:05, 11 February 2009

« previous mtg | index | next mtg »

Discussion Items

  • QA Q109 Workweek (marcia) 2/17-2/20
    • List is pretty full. Anything else to add?
  • QMO stuff (marcia)
    • Style Guide/Community Leads
      • It has become clear that we need to both have a process for promoting people to Community Leads as well as some control over people adding content. Today I noticed that someone had added "It's okay we don't bite" to the Community FAQ - I edited that content out, but we can't just let people add content willy nilly. There needs to be some sort of review process. One thing that Tomcat mentioned is to have people create bugs and then have a QA team member review + the document just like a patch.
      • discussion - should have a vetting process for community members who want admin access. (marcia) and (tomcat) to work on a guide to demonstrate they are behaving properly.
        • Any update on this?
      • discussion - for content issues, should we review what content is posted before allowing it on QMO? (marcia) and (tomcat) to work on a policy guide.
        • Any update on this?
      • Opinion: Defining guidelines and expecting contributors to follow those guidelines is a good idea. However, throwing up road blocks to the community is a terrible idea. This isn't software code that requires a review process to protect an application. Just deal with inappropriate content as it shows up. Has it been an overwhelming problem so far? (Tracy)

Project Updates

  • Firefox 3.0.7 (abillings)
  • Firefox 3.1 (tchung)
    • Beta 3 Testplan
      • Builds hand to QA - Still no word.
      • QA test signoff - +5 days
    • Tracking Status page
      • Update your testing progress percentages
  • 3.0 -> 3.1b3 major update trial run (abillings)
  • Webdev update (stephend)
  • Mobile update (jmaher)
  • Litmus results cleanup project (tracy)
  • Accessibility update (MarcoZ)

Other topics?

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Execution/Meetings/2009-02-11&oldid=128468"