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

From MozillaWiki
Jump to navigation Jump to search
(added a couple missing bullets)
(Aug 24th confidence assessments entered)
Line 1: Line 1:
__NOTOC__
__NOTOC__
<big><big>'''August 2, 2017'''</big></big>
<big><big>'''August 24, 2017'''</big></big>


== OKR Progress ==
== OKR Progress ==
Line 16: Line 16:
|style="text-align: center; background-color: #f9d9a8"|Jul 25
|style="text-align: center; background-color: #f9d9a8"|Jul 25
|style="text-align: center; background-color: #f9d9a8"|Aug 2
|style="text-align: center; background-color: #f9d9a8"|Aug 2
|style="text-align: center; background-color: #f9d9a8"|Aug 16
|style="text-align: center; background-color: #f9d9a8"|Aug 24
|style="text-align: center; background-color: #f9d9a8"|Aug 30
|style="text-align: center; background-color: #f9d9a8"|Sep 7
|style="text-align: center; background-color: #f9d9a8"|Sep 13
|style="text-align: center; background-color: #f9d9a8"|Sep 21
|style="text-align: center; background-color: #f9d9a8"|Sep 27
|style="text-align: center; background-color: #f9d9a8"|Score
|-
|-
|rowspan=2| 1. To enable bi-directional bookmarks on iOS by Firefox 57.
|rowspan=2| 1. To enable bi-directional bookmarks on iOS by Firefox 57.
Line 29: Line 29:
|align="center"|65%
|align="center"|65%
|align="center"|65%
|align="center"|65%
|align="center"|
|align="center"|95%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 40: Line 40:


|
|
*Went unexpectedly well. Has landed.
*So far so good with the internal testing. Looks great. Softvision testing is underway.
|-
|-
|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 48: Line 48:
|align="center"|50%
|align="center"|50%
|align="center"|50%
|align="center"|50%
|align="center"|
|align="center"|95%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
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]  
|
|
*Also going well.   
*Same as with 1.1 - looks great. Softvision testing is underway.   
|-
|-
|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 67: Line 67:
|align="center"|50%
|align="center"|50%
|align="center"|75%
|align="center"|75%
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
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]
|
|
*Work is progressing and results are looking good.
*Largely done. The data looks good. Just needs to be written up at this point.
 
*Analyst hired and starts on Aug. 28th.
 
 
Risks:
*Assume we won’t hire an analyst by end of Q3 to support our team.
|-
|-
| 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 88: Line 84:
|align="center"|50%
|align="center"|50%
|align="center"|60%
|align="center"|60%
|align="center"|
|align="center"|60%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 97: Line 93:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1381643 Bug 1381643: Create bookmark validation dashboard]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1381643 Bug 1381643: Create bookmark validation dashboard]
|
|
*Still blocked on the pre-requisite of landing a bookmark validator for Android, but this has been reviewed and is almost ready.
*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.
Risks:
*Android validation data aren’t in yet.
*What’s the status of iOS sending pings? Landed, but we need to make sure they’re sent/received.
*Is our analysis correct? If not, we risk creating dashboards that don’t answer our questions.
 
|-
|-
| align="left"|2.3 Flatten Sync engine data.
| align="left"|2.3 Flatten Sync engine data.
Line 112: Line 103:
|align="center"|50%
|align="center"|50%
|align="center"|60%
|align="center"|60%
|align="center"|
|align="center"|80%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 121: 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]
|
|
*A lot of work has been completed but with mixed results.
*Flattening up the data is done and looks good. Hasn’t landed yet.
*Have permission to do it in Scala and look at why it’s crashing the way it is.  
|-
|-
| align="left"|2.4 Stand up Sync Engine Dashboards.
| align="left"|2.4 Stand up Sync Engine Dashboards.
Line 130: Line 120:
|align="center"|40%
|align="center"|40%
|align="center"|40%
|align="center"|40%
|align="center"|
|align="center"|60%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 138: Line 128:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1381643 Bug 1381643: Create bookmark validation dashboard]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1381643 Bug 1381643: Create bookmark validation dashboard]
|
|
*Dependent upon 2.3.
*Unknown about how long the queries will take when run across engines.
*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 146: Line 137:
|align="center"|50%
|align="center"|50%
|align="center"|55%
|align="center"|55%
|align="center"|
|align="center"|50%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 154: Line 145:
*[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]
|
|
*Have been conducting some analysis of the validation and forming some ideas.
*Need to work out as a team what our strategy is...a MetricsFest.
*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.
|-
|-
|rowspan=4| 3. To prevent bookmark corruption.
|rowspan=4| 3. To prevent bookmark corruption.
Line 166: Line 158:
|align="center"|70%
|align="center"|70%
|align="center"|80%
|align="center"|80%
|align="center"|
|align="center"|95%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 173: Line 165:
*[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]
|
|
*Agreed to move bookmark management to 57. Work itself is largely done. Some remaining changes will be done this week.
*It landed. Seems to work well.  
*This work will make the work for 3.2 easier.
*The core of the work is done, and there shouldn’t be much follow-on work.
 
|-
|-
| align="left"|3.2 Prevent re-ordering of bookmarks on Android.
| align="left"|3.2 Prevent re-ordering of bookmarks on Android.
Line 182: Line 175:
|align="center"|50%
|align="center"|50%
|align="center"|60%
|align="center"|60%
|align="center"|
|align="center"|60%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 190: Line 183:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1352947 Bug 1352947: Android writes many root folders with children missing or in the wrong order]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1352947 Bug 1352947: Android writes many root folders with children missing or in the wrong order]
|
|
*Have made progress on 3.1.
*Have discovered other problems.
*Need to improve deduping, deletion tracking, timestamp-based change tracking.
*Have started on improvements but nothing has landed yet.
|-
|-
| 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 198: Line 193:
|align="center"|60%
|align="center"|60%
|align="center"|75%
|align="center"|75%
|align="center"|
|align="center"|85%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 208: Line 203:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1305563 Bug 1305563: Buffering and two-phase application for Desktop]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1305563 Bug 1305563: Buffering and two-phase application for Desktop]
|
|
*Understand how iOS merge works now. Ported it to desktop. Merged trees can apply back to Places now.
*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.
|-
|-
| align="left"|3.4 Batch upload API enabled for all users, with more than 99% of uploads fitting into a single atomic batch.
| align="left"|3.4 Batch upload API enabled for all users, with more than 99% of uploads fitting into a single atomic batch.
Line 214: Line 211:
|align="center"|75%
|align="center"|75%
|align="center"|80%
|align="center"|80%
|align="center"|
|align="center"|80%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 223: Line 220:
*[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]
|
|
*Work is progressing well.
*Still risk involved because we're still seeing 503s with batch uploads.
|-
|-
|}
|}

Revision as of 23:19, 25 August 2017

August 24, 2017

OKR Progress

Objective Key Result Confidence Features Notes
Jul 6 Jul 25 Aug 2 Aug 24 Sep 7 Sep 21 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%

Bookmarks are Sync'd from iOS to desktop.

  • So far so good with the internal testing. Looks great. Softvision testing is underway.
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%

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

  • Same as with 1.1 - looks great. Softvision testing is underway.
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%

Validated validation data

  • Largely done. The data looks good. Just needs to be written up at this point.
  • Analyst hired and starts on Aug. 28th.
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%

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%

Provide better sync engine error data for dashboards.

  • Flattening up the data is done and looks good. Hasn’t landed yet.
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%

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%

Implementation of a Repair Failure Strategy

  • Need to work out as a team what our strategy is...a MetricsFest.
  • 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.
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% Version-based syncing of bookmarks
  • It landed. Seems to work well.
  • The core of the work is done, and there shouldn’t be much follow-on work.
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%

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.
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%

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%

Batch upload API enabled

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