QA/StaffMeetings/QA-Staff-06-08-2011

« previous mtg | QA Staff Home | next mtg »

QA Staff Meeting Notes June 8, 2011

New Hires

• James Bonacci, Services QA Lead! Start date: June 20th

Vacation Calendar for June

• Matt: May 28- June 18
• Tracy: June 10
• Henrik: June 3-17
• Stephen: June 3-8
• Aakash: June 17-20
• Naoki: June 30 - July 5
• Dave Hunt: June 7-14
• Vishal: Friday, June 10

Upcoming Test Events

• Friday, June 10th: Developer Tools Testday (ashughes)

Project Status

• Overview (2 min brief update)

Desktop Firefox (Juan)

• CrashKill
  • Stability Report
  • Entire directory drilled down by versions

Browser Technologies (Tony)

• Fennec (aakash)

• Sync (Tracy)

• Load Testing (Owen)

• Test pilot (tracy)

• Identity (tracy)

• Firefox Home (nhirata)
  • Initial Testing has started on testbed
  • Still need to get some of the infrastructure setup
    • Dev hoping to get most of it setup in about a month

WebQA (Stephen)

AMO

• AMO 6.0.12 went live 06/02
• AMO 6.1.1 is scheduled to go live on 06/08
• We ran the add-on bulk compatibility check for Firefox 6.*

Engagement Projects

• Mark Up dark launched on 6/7, snippets push on 6/9

Input

• Push 4.0.3/4.1 milestone 6/8

Socorro

• 1.7.8 milestone pushed 6/2
• 2.0 milestone slated for 6/21

SUMO

• SUMO 2011-06-07 release goes out 6/7
• SUMO 06-14 release for next week

WebQA Automation

AMO

• Still working through Code reviews. Are still getting pull requests from contributors

SUMO

• New test for user registration

Community (Marcia)

• Weekly Community Scrumpad has very little participation (ashughes and marcia are the sole contributors). Please add any items and events you are working on so we can track what other efforts are ongoing related to community.
• Update from Mary re: events:
  • Contributor Engagement now needs to dive in and develop a list of events that make sense to go to in order to drive participation. Additionally, they will need to work with teams to see if they have events that make sense for them to drive contribution.
  • BlogHer contribute event will likely not happen unless we can quickly mobilize some contributors and get on the agenda as a BOF.
• There is now a bi-weekly Contribute Group meeting.
  • The Contribute Group is a forum for discussing ideas, questions, concerns or anything else about bringing new people into Mozilla.
    • Meeting time: Every other Thursday at 10 AM PDT
    • Dial-in information: 1-800-707-2533, pin: 369, conf: 634
    • Back channel: irc.mozilla.org#mozillians
    • Agenda: https://wiki.mozilla.org/Mozilla.org/Contribute#Meetings
• David Boswell has a new post about the Mozilla Community: http://davidwboswell.wordpress.com/2011/06/07/who-is-in-the-mozilla-community/

Discussion Items

• Goals
  • Report and update your Q2 goals progress in the next 2 weeks
  • Have Q3 completed by july 1st. Team leads, and individuals, get your proposed goals drafted in the next weeks
    • These are going to be the benchmark for future team performance, individual performance.
• Questions/Feedback on new org structure? Matt is announcing to rest of group when he gets back
• (cont) handle bugzilla tracking of fixed and verified bugs in rapid release branch? (aurora, beta) (juanb, tchung)
• Contributor emails update (juanb)
• MozillaQA Twitter Account. has this been resolved?
• Proxy based testing (al)
• QMO Pages thoughts (owen). Take a look and comment

Notes, Takeaways and Action Items

Today

• Add notes here

Last Meeting

• Introductions: Owen started this week. Geo is his mentor. Welcome!
• Meetup Tonight: Selenium, 6:30pm, more greeters welcome.
• Go-no-go criteria from QA
  • What will constitute this criteria? (geo) - Work in progress. Draft this week. (juanb)
• Vacation:
  • Organizational changes in the teams to be articulated before then. (mevans)
• Scrumpad: We depend on this information day-to-day, and it's becoming more important to others.
  • Leads responsible to update the highlights by Friday.
  • Any other pertinent information like other meetings' notes would be useful
• Use of Pivotal for tracking purposes. Cameron presented a brief intro to the system he uses to keep track of his projects.
  • Check it out and see if it meets your needs. You are encouraged to use it, and we could make a decision to adopt it in a few weeks. (mevans)
• Contributor inquiries responses: How do we go forward?
  • Any mail client solution to do automated responses is good for now. (juanb)
  • Figure out an interim solution to this. (juanb, mevans, et al interested)