User Services/Sync/Migration

General discussion of migration issues for Sync.next. The product owner and team have not made final decisions on these issues.

New Sync Users

• No migration issues, just use FxA for the first time.
• All Fx29 will prompt with FxAccount flow, informed that < Fx29 won't sync with this account.
• If user has Fx28, they should see warning that this is deprecated? (guess)

Existing Sync user

• If they manually chose to use Sync.next, they would be informed that all < Fx29 devices will not sync to > Sync.next.
• Firefox clients would detect if sync account clients all use > Fx29, then message user to use sync.next - FxA flow.

Fx29

• Will Sync.old and Sync.next be in Fx29?
  • This is a sticking point for existing users who have/do not want to upgrade at that time.

Sync Server

• v1.5 API is being discussed, not sure the outcome.
• There will be two DBs: Sync 1.1 and Sync 1.5 will point at different DBs

Channels

• Feature will be off and enabled via pref in Nightly/Aurora/Beta
  • increases risk as little public user testing
  • Since it's behind pref, FxAccount user may have to be recreated, Sync data is not guaranteed.

PROPOSED: Need a high visibility blog post for users to try out sync using test profiles.

Custom Servers

• Do we allow for use of custom sync server?
  • Will they still be able to use FxA in this flow?

PROPOSED: No UI for this, but about:config paths can be modified to support custom servers.