Milestones this Quarter

This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.

Milestone	Date	Delight	Dependability	Security & Privacy	Performance	Overall Score	Rationale
Firefox Ten Year	Nov 9
Firefox 33	Oct 13
Firefox 34	Nov 25
PDX Work week	Dec 1 - 6
Marketplace shift to FxAccounts	Oct 31
Marketplace ship on Tarako Device in new location	Oct - Nov
QMO Update	Nov 20?
MozFest	Oct 24-26
Firefox OS 2.1	Nov 30
Loop Ship	Nov 25
E10S on by default in nightly	Nov 9

General Quality

[ON TRACK] Create a centralized site of all dashboard/project information from all quality teams (opt in, per team) so that it is easier to understand the impact and effect of on-going quality efforts
- [ON TRACK] [ctalbert] Add churn metrics to the dashboard for platform codebase
- [ON TRACK] [mschifer] Include SUMO metrics for support requests over time
- [ON TRACK] [bsilverberg] Identify and produce metrics around the "drop-off rate" of One and Done tasks for tracking
- [ON TRACK] [ctalbert] Invite services QA to add in relevant, high level dashboards for cross-QA projects (like Loop, FxAccounts etc)
[ON TRACK] Deploy a simpler, streamlined version of QMO
- [DONE] [pragmatic] Consolidate all QA Docs onto MDN and/or Moz Wiki as appropriate
- [ON TRACK] [aaronmt] Use our social media presences for digital outreach to create a bit of buzz around the QMO deployment measured by an increase in number of first time contributors
[ON TRACK] [aaronmt/ashughes] Testdays: Based on feedback gathered in Q3, prioritize and resolve some of the barriers to participation with a goal of developing some contributors engaged outside of these events (ex. active in bugzilla/moztrap/one&done day-to-day).
- Hypothesis: if we provide more frequent bite-sized mentorship opportunities through testdays we'll develop more established relationships in other contribution channels

[ON TRACK] [mschifer] Work on doing fewer verifications since they don't seem to be effective, and use the time saved for exploratory testing.
- Hypothesis: We will still produce releases just as high quality but will be able to find more interesting bugs sooner in the development cycles.
- Hypothesis: We will be able to use our fledgling churn metrics to guide where and when to do verifications for non-security bugs (all security bugs continue to be verified if possible).
[ON TRACK] [lizzard] Clarify/standardize/improve how we do QA for Firefox through the entire release process. Have a fairly standard wiki template for each Firefox channel that we can use for tracking and for our daily workflow. We can support community better in helping us (and support each other) better if we have a good transparent window into how QA works across each "train"
[ON TRACK] [mschifer] Develop a system to measure development pace for SV Automation (similar to FxTeam) so we can establish a historical baseline and begin to measure an increase pace of automated test development

[ON TRACK] [mbrandt and shared with MDN dev] Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept) which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:
[ON TRACK] [MDN] identify, document, and prioritize current testing challenges and needs (we've already done most of this,I think -- it's mostly a matter of collating/articulating clearly)
[ON TRACK] [mbrandt] create the plan (incl. decisions, next steps/action items, owners, dependencies, agreed-upon process/workflow changes, etc.) to best-attempt to address those needs
[ON TRACK] [mbrandt] execute against the plan -- according to decided owners -- noting new dependencies, shifts in direction, limitations, etc.
[ON TRACK] [mbrandt] at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015
[ON TRACK] [rbillings] Review current commitments in terms of projects and transition several to community and/or developers until the set of sites is both sustainable and our time spent on them is impactful
[ON TRACK] Finalize marketplace support requirements for Firefox OS
- [ON TRACK] [krupa] Ensure automation runs on 2.0 using Flame devices set for 319Mb of RAM to simulate Tarako
  - depends on bug 1020536, which itself depends on bug 1011016
- [ON TRACK] [krupa] Have automation coverage for Payments including in-app payments
  - depends on bug 1015251 and bug 1083528

[ON TRACK] [sydpolk/nils] Complete WebRTC connection establishment and connection quality tests by deploying them to the automation created in Q3 and have them reporting to Treeherder
[ON TRACK] [sydpolk/nils] Start and deliver at least one sprint on a new (non-WebRTC) project - project TBD, likely one of: (gfx hardware discovery, MSE)

[ON TRACK] [ctalbert] Create the long term 2015 plan for community that addresses how we move our contributors from one-time contributors to active and core contributors
[DONE] [marcia] Participate in the Mozilla Spaces Bug Squash November 1-2 (London and Paris offices) with the explicit goal of getting more QA ideas and process instilled in Firefox OS contributors
[DONE] [marcia] Participate in the Mozilla Festival October 24-26 with the goal of sharing QA best practices around FX OS, and give community the setup they need to make in an impact in the project.
[ON TRACK] [bsilverberg] One and Done: Build a metrics dashboard that exposes data on the most completed & most abandoned tasks, identifying contributors who are making an impact
[ON TRACK] [ctalbert, aaronmt, rbillings, ashughes, marcia] Use Community Calls, new testdays, community buddy, etc as a bridge between one and done and the larger community in order to help contributors cross the gap between "doing something in one and done" and being an active contributor.
- Hypothesis: if we execute well on these initiatives we'll see a decline in the drop-off rate between 1 task contributors and multiple task contributors and we can use that to see if these efforts are successful.
[ON TRACK] [pragmatic] QMO Re-design: Complete the migration of Docs off QMO to MDN QA Zone. Roll the new design on to the live site.