Firefox/Sync/Progress Report/2017Q3: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(corrected typo)
(Entered updates for Sept. 18)
Line 18: Line 18:
|style="text-align: center; background-color: #f9d9a8"|Aug 24
|style="text-align: center; background-color: #f9d9a8"|Aug 24
|style="text-align: center; background-color: #f9d9a8"|Sep 7
|style="text-align: center; background-color: #f9d9a8"|Sep 7
|style="text-align: center; background-color: #f9d9a8"|Sep 21
|style="text-align: center; background-color: #f9d9a8"|Sep 18
|style="text-align: center; background-color: #f9d9a8"|Score
|style="text-align: center; background-color: #f9d9a8"|Score
|-
|-
Line 30: Line 30:
|align="center"|65%
|align="center"|65%
|align="center"|95%
|align="center"|95%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|100%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 40: Line 40:


|
|
*So far so good with the internal testing. Looks great. Softvision testing is underway.
*Done!
|-
|-
|align="left"| 1.2 Users can delete their mobile bookmarks from their iOS device.
|align="left"| 1.2 Users can delete their mobile bookmarks from their iOS device.
Line 49: Line 49:
|align="center"|50%
|align="center"|50%
|align="center"|95%
|align="center"|95%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|100%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 57: Line 57:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1387492 Bug 1387492: Allow remote Mobile Bookmarks]  
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1387492 Bug 1387492: Allow remote Mobile Bookmarks]  
|
|
*Same as with 1.1 - looks great. Softvision testing is underway.  
*Done!  
|-
|-
|rowspan=5| 2. To have our data provide valuable insights about Sync engine errors and bookmark validation.
|rowspan=5| 2. To have our data provide valuable insights about Sync engine errors and bookmark validation.
Line 68: Line 68:
|align="center"|75%
|align="center"|75%
|align="center"|90%
|align="center"|90%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 75: Line 75:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1381642 Bug 1381642: Validate bookmark validator dashboards with ad-hoc analysis]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1381642 Bug 1381642: Validate bookmark validator dashboards with ad-hoc analysis]
|
|
*Largely done. The data looks good. Just needs to be written up at this point.
*Largely done. The data looks good.  
*Analyst hired and starts on Aug. 28th.
*Just needs to be written up at this point.
|-
|-
| align="left"|2.2 Stand up dashboards with accurate bookmark validation data from Android and iOS.
| align="left"|2.2 Stand up dashboards with accurate bookmark validation data from Android and iOS.
Line 85: Line 85:
|align="center"|60%
|align="center"|60%
|align="center"|60%
|align="center"|60%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|60%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 104: Line 104:
|align="center"|60%
|align="center"|60%
|align="center"|80%
|align="center"|80%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 112: Line 112:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1381641 Bug 1381641: Flatten Sync Engine data]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1381641 Bug 1381641: Flatten Sync Engine data]
|
|
*Flattening up the data is done and looks good. Hasn’t landed yet.
*Flattening up the data is done, and it's landed.  
*Needs verification.
|-
|-
| align="left"|2.4 Stand up Sync Engine Dashboards.
| align="left"|2.4 Stand up Sync Engine Dashboards.
Line 121: Line 122:
|align="center"|40%
|align="center"|40%
|align="center"|60%
|align="center"|60%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|60%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 129: Line 130:
|
|
*Unknown about how long the queries will take when run across engines.
*Unknown about how long the queries will take when run across engines.
*2.2 is a blocker for 2.4
*2.2 is a blocker or 2.4
|-
|-
| align="left"|2.5 Formulate concrete action items from the validation and sync engine data.
| align="left"|2.5 Formulate concrete action items from the validation and sync engine data.
Line 138: Line 139:
|align="center"|55%
|align="center"|55%
|align="center"|50%
|align="center"|50%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|30%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 145: Line 146:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1340325 Bug 1340325: Define and implement repair failure strategy]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1340325 Bug 1340325: Define and implement repair failure strategy]
|
|
*Need to work out as a team what our strategy is...a MetricsFest.
*Not as high of a priority now that we have bi-directional sync working.
*To get done with 2.5 by the end of the quarter, we shouldn’t take much longer than mid-Sept. to finish 2.2 and 2.4.
*Still needs some sort of resolution.
*Now have Leif to help with the analysis of the data.
|-
|-
|rowspan=4| 3. To prevent bookmark corruption.
|rowspan=4| 3. To prevent bookmark corruption.
Line 159: Line 161:
|align="center"|80%
|align="center"|80%
|align="center"|95%
|align="center"|95%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|95%
|align="center"|
|align="center"|
|Version-based syncing of bookmarks
|Version-based syncing of bookmarks
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1364644 Bug 1364644: Version-based syncing of bookmarks]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1364644 Bug 1364644: Version-based syncing of bookmarks]
|
|
*It landed. Seems to work well.  
*This work is being tested by Softvision.
*The core of the work is done, and there shouldn’t be much follow-on work.
*So far, all the identified issues have been fixed.
 
|-
|-
| align="left"|3.2 Prevent re-ordering of bookmarks on Android.
| align="left"|3.2 Prevent re-ordering of bookmarks on Android.
Line 176: Line 177:
|align="center"|60%
|align="center"|60%
|align="center"|60%
|align="center"|60%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|50%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 186: Line 187:
*Need to improve deduping, deletion tracking, timestamp-based change tracking.
*Need to improve deduping, deletion tracking, timestamp-based change tracking.
*Have started on improvements but nothing has landed yet.
*Have started on improvements but nothing has landed yet.
*Slight downgrade in confidence to show that there’s still work to get done by the end of the quarter. Want to start working on this this week.
|-
|-
| align="left"|3.3 Analyze and prevent erroneous bookmark deduping on Desktop.
| align="left"|3.3 Analyze and prevent erroneous bookmark deduping on Desktop.
Line 194: Line 197:
|align="center"|75%
|align="center"|75%
|align="center"|85%
|align="center"|85%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 212: Line 215:
|align="center"|80%
|align="center"|80%
|align="center"|80%
|align="center"|80%
|align="center"|
|align="center"|--
|align="center"|
|align="center"|80%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 220: Line 223:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1378569 Bug 1378569: Increase max records per batch so ~99% of sync users are able to post all their bookmarks in a single batch]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1378569 Bug 1378569: Increase max records per batch so ~99% of sync users are able to post all their bookmarks in a single batch]
|
|
*Still risk involved because we're still seeing 503s with batch uploads.
*Still risk involved because still seeing 503s with batch uploads.
|-
|-
|}
|}

Revision as of 00:58, 19 September 2017

August 24, 2017

OKR Progress

Objective Key Result Confidence Features Notes
Jul 6 Jul 25 Aug 2 Aug 24 Sep 7 Sep 18 Score
1. To enable bi-directional bookmarks on iOS by Firefox 57.

User story: As an iOS user, I’d like to see my existing mobile bookmarks on my desktop.

1.1 Users can see their mobile bookmarks on desktop. 50% 65% 65% 95% -- 100%

Bookmarks are Sync'd from iOS to desktop.

  • Done!
1.2 Users can delete their mobile bookmarks from their iOS device.

We don’t want to prevent users from deleting their mobile bookmarks from the mobile device.

50% 50% 50% 95% -- 100%

Ability to delete mobile bookmarks from iOS device and Sync those deletions to desktop.

  • Done!
2. To have our data provide valuable insights about Sync engine errors and bookmark validation. 2.1 Validate our validation data.

(Desktop, iOS and Android)

We don’t have confidence that our validation data query results and if they tell us what we want to know. Our analyses tell us different things depending on how they’re run. Let’s get a third party to review the validity of our queries and results.

50% 50% 75% 90% -- 90%

Validated validation data

  • Largely done. The data looks good.
  • Just needs to be written up at this point.
2.2 Stand up dashboards with accurate bookmark validation data from Android and iOS.

Make sure that the Android and iOS pings are coming in and land the data in Presto in order to create dashboards.

50% 50% 60% 60% -- 60%

Bookmark validation dashboards for iOS and Android

  • Android and iOS are landed.
  • Data seems good, but it doesn’t seem to be refreshed.
  • Might need to dig into the data a little more.
2.3 Flatten Sync engine data.

The engine data are currently unusable for creating dashboards. We need to flatten, have confidence in our results so that we can prioritize our fixes for Desktop.

50% 50% 60% 80% -- 90%

Provide better sync engine error data for dashboards.

  • Flattening up the data is done, and it's landed.
  • Needs verification.
2.4 Stand up Sync Engine Dashboards.

Using the flattened Sync engine data, stand up dashboards and have confidence in the analysis.

40% 40% 40% 60% -- 60%

Bookmark Validation Dashboard

  • Unknown about how long the queries will take when run across engines.
  • 2.2 is a blocker or 2.4
2.5 Formulate concrete action items from the validation and sync engine data.

Create a backlog of prioritized bugs to be addressed as a result of our data discoveries.

60% 50% 55% 50% -- 30%

Implementation of a Repair Failure Strategy

  • Not as high of a priority now that we have bi-directional sync working.
  • Still needs some sort of resolution.
  • Now have Leif to help with the analysis of the data.
3. To prevent bookmark corruption. 3.1 Land the bookmark Sync tracker on Android.

In support of Full Bookmark Management that’s being introduced in 56.

Needs to land in nightly by: July 31st (56 goes to Beta on August 7).

50% 70% 80% 95% -- 95% Version-based syncing of bookmarks
  • This work is being tested by Softvision.
  • So far, all the identified issues have been fixed.
3.2 Prevent re-ordering of bookmarks on Android.

There is a recurring problem where users bookmarks are re-ordered on their mobile device. Fix this.

50% 50% 60% 60% -- 50%

Prevention of bookmark reordering on Android.

  • Have discovered other problems.
  • Need to improve deduping, deletion tracking, timestamp-based change tracking.
  • Have started on improvements but nothing has landed yet.
  • Slight downgrade in confidence to show that there’s still work to get done by the end of the quarter. Want to start working on this this week.
3.3 Analyze and prevent erroneous bookmark deduping on Desktop.

There is a problem where users’ bookmarks are incorrectly deduped or reordered on their desktop device. This is a form of data loss.

60% 60% 75% 85% -- 90%

Feature description(s)

  • A lot of work has been completed over the past couple weeks.
  • Good initial feedback; needs more test coverage for edge cases.
  • Targeting final review or landing pref’d off by the end of the quarter.
3.4 Batch upload API enabled for all users, with more than 99% of uploads fitting into a single atomic batch. 50% 75% 80% 80% -- 80%

Batch upload API enabled

  • Still risk involved because still seeing 503s with batch uploads.