User:Ashughes/Status/2013/10
< User:Ashughes | Status
Jump to navigation
Jump to search
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
- [DONE] Identify Moztrap regression tests for automation [wiki]
- Firefox 21
- [BLOCKED] Sign-off Firefox 21 stub installer testing [testplan]
- Firefox 19
- [DONE] Complete action items from Fx19 post-mortem
Accomplishments
- Reported 1 regression (bug 849347)
- Qualified click-to-play blocklisting for Flash 10.3 on Firefox 19+ (bug 848002)
- Coordinate Aurora stub installer testing
- Verified fixed 1 bug (bug 819141)
- Signed-off and shipped Firefox 19.0.2 (0-day chemspill)
- Signed-off and shipped Firefox 17.0.4esr (0-day chemspill)
- Identified 10 bugs for potential Mozmill automation
- Completed action items from Firefox 19 post-mortem
- Began on-boarding 4 new community members
Upcoming
Monday
- Automation
- Update status on mozmill-ci l10n expansion (issue 211)
- Update status on mozmill metro tests (bug 845079)
- Identify SocialAPI tests for automation
- Aurora Stub Installer
- [ON TRACK] Sign-off Firefox 21 stub installer testing [testplan]
- Professional Development
- Create a page to track quarterly accomplishments
- Take next steps toward finding a mentor
- Catalog and challenge my assumptions
- Develop a role for a community manager in my team vision
- Need to fill position for a community manager (someone to wrangle people, foster accountability, steer team along a road map) -- Tracy???
- Also add need to be more proactive and vocal, don't wait for someone to grant us a voice, lessons learned from B2G QA
- Social API
- Activate and dogfood mixi support
Tuesday
- Firefox 21
- QAWANTED bug triage
- dev-platform
- Propose auto-verification of bugs with in-testsuite+
- Community Engagement
- Create a project page for contributing to Firefox release process
Wednesday
- Softvision Standup
- Review status of Firefox 19 post-mortem action items
- Firefox
- Update Firefox Release Metrics document
- Rapid Betas
- Ping joduinn re moving go-to-build -1 day and go-to-release +1 day
- Update and review Rapid Betas QA strategy with Juan, Marcia, Otilia, and Ioana
Thursday
- Firefox 21
- QAWANTED bug triage
- Documentation
- Revise and simplify Bug Triage document, integrate with B2G Triage document
Friday
- Firefox 21
- mozilla-aurora pushlog triage
- 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)
- 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