670
edits
(Updated comments for objectives 1 and 2) |
(completed updates for objective 3) |
||
| Line 50: | Line 50: | ||
| | | | ||
*Done! | *Done! | ||
*Completed 13 out of | *Completed 13 out of 22, or 59%. | ||
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown] | *[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown] | ||
|- | |- | ||
| Line 66: | Line 66: | ||
*[https://github.com/mozilla/fxa-content-server/pull/5332 Issue 5332: ABC test for CAD phase 3 (deep link)] | *[https://github.com/mozilla/fxa-content-server/pull/5332 Issue 5332: ABC test for CAD phase 3 (deep link)] | ||
| | | | ||
* | *Didn't achieve this. Had a lot of questions about the metrics. | ||
|- | |- | ||
|align="left"| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device. | |align="left"| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device. | ||
| Line 84: | Line 83: | ||
|rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile. | |rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile. | ||
| align="left"|2.1 Measure and A/B test best push opt-in screen on iOS. | | align="left"|2.1 Measure and A/B test best push opt-in screen on iOS. | ||
|align="center"|50% | |align="center"|50% | ||
| Line 109: | Line 107: | ||
|align="center"|0.8 | |align="center"|0.8 | ||
|align="left"| | |align="left"| | ||
Identification and fixing of the most impactful bugs on iOS | Identification and fixing of the most impactful bugs on iOS | ||
| | | | ||
*8 out of 13 are done - 80% of 80% done as of 9/25 | *8 out of 13 are done - 80% of 80% done as of 9/25 | ||
| Line 130: | Line 123: | ||
|align="left"| | |align="left"| | ||
*Allow users to test out device pairing. This does not necessarily mean that QR codes are used. | *Allow users to test out device pairing. This does not necessarily mean that QR codes are used. | ||
| | | | ||
*Pushed forward the auto-focus | *Pushed forward the challenge with auto-focus. | ||
* | *There are things we got done this quarter that we can roll forward. | ||
*Great analysis | *Great analysis. | ||
|- | |- | ||
| align="left"|3.2 Ship secondary email. | | align="left"|3.2 Ship secondary email. | ||
| Line 146: | Line 138: | ||
| | | | ||
*We are allowing users to add a secondary email. Allows users to change primary email. | *We are allowing users to add a secondary email. Allows users to change primary email. | ||
| | | | ||
*Caching bug fixed | *Caching bug fixed | ||
Client code is in | *Client code is in | ||
Works for AMO,and they have an issue to fix one little thing | *Works for AMO, and they have an issue to fix one little thing | ||
Pocket was the only remaining thing. | *Pocket was the only remaining thing. | ||
|- | |- | ||
| align="left"|3.3 Land support for relier encryption keys. | | align="left"|3.3 Land support for relier encryption keys. | ||
| Line 171: | Line 155: | ||
Relier encryption keys | Relier encryption keys | ||
| | | | ||
* | *Have done a lot of good work on it but it’s not totally closed out. | ||
*Still working on the reviews. | |||
*Currently under scrutiny by two crypto specialists. | |||
*Can’t ship until we clear the security reviews. | |||
*[https://github.com/mozilla/fxa/issues/245 Issue 245: Prototype key support api for Firefox Notes] | *[https://github.com/mozilla/fxa/issues/245 Issue 245: Prototype key support api for Firefox Notes] | ||
|- | |- | ||
| Line 185: | Line 172: | ||
Implementation of Amplitude | Implementation of Amplitude | ||
| | | | ||
* | *Should be collecting real-time data this week. | ||
* | *We’ve haven’t completely tied everything off, but it’s basically done. | ||
* | *Working in stage and currently fine tuning. | ||
|- | |- | ||
|} | |} | ||
edits