User:Ashughes/Status/2013-03-08

Status for March 4-8, 2013

Goals

Monday

• N/A - Offline due to internet outage

Tuesday

• N/A - Offline due to attendance at BSides Vancouver 2013

Wednesday

Automation

• [DONE] Report issue to track expansion of mozmill-ci testruns to de and it locales (mozmill-ci:211)
• [DONE] Nominate new endurance test candidates: bug 834667, bug 839548, bug 837845

Blocklisting

• [DONE] Test staged blocklist for Flash 10.3 (bug 848002)
• [DONE] Test production blocklist for Flash 10.3 (bug 848002) - pending push to production

Firefox 19

• [DONE] Archive post-mortem notes to the wiki page
• [ON TRACK] Complete action items from Fx19 post-mortem

Firefox 21

• [DONE] Coordinate stub installer testing [wiki]

Social API

• [DONE] Verify fixed bug 819141

Thursday

Firefox 21

• [DONE] QAWANTED bug triage

Firefox 19

• [DONE] Coordinate testing and sign off Firefox 19.0.2 for bug 848644

Firefox 17esr

• [DONE] Coordinate testing and sign off Firefox 17.0.4esr for bug 848644

Friday

Automation

• Identify SocialAPI tests for automation

Documentation

• Create a document on QMO for testing throttled/unthrottled updates manually
• Create a document on QMO for testing blocklists
• Create a document on QMO for using mozregression (maybe a video too)

Firefox Desktop

• Create a page to track per-release QA metrics [wiki]
  • To include # of respins, # bugs verified, # bugs fixed, # bugs affected, #bugs wontfix, ADIs prior to next release
• Update policy draft for improving bug triage effectiveness [wiki]

Professional Development

• Create a page to track quarterly accomplishments

Rapid Betas

• Update and review Rapid Betas QA strategy with Juan, Marcia, Otilia, and Ioana

Testdays

• Move testday metrics to it's own page [wiki]
• Move contributors wiki to it's own page (include @contribute, expertise, platforms) [wiki]
• Create a document on QMO to showcase contributors [wiki]
• Reach out to contributors who've not contributed in >2 months
• Organize a memshrink for add-ons testday [wiki]
• Create a draft proposal for Testday and Release QA contributor conversion points
• Create a draft proposal for a Testday Framework
  • Ideas include: add a testday component to bugzilla for people to request and vote on testdays, evaluate role of existing tools (wiki, qmo, mailing list, etherpad, irc, moztrap, testdaybot), speak to team leads about testday fatigue, geo-distributed 2h sprints, community leadership, documentation days, bug days, rewards/recognition, conversion points, look at what other teams are doing (fedora, ubuntu, bugmasters, etc), identify and resolve pain points, promote leaders, improve accessibility, learning days, dashboarding/metrics, developer engagement, hours of operation, mentors and moderators, improve clarity of instructions/expectations, improve accountability

Upcoming

Monday

Automation

• Update status on mozmill-ci l10n expansion (issue 211)
• Update status on mozmill metro tests (bug 845079)