1023083 - [UX] Clarify migration UX around "eol" trigger and self-hosted users.

Status: RESOLVED FIXED

(Firefox :: Sync, defect)

Description

[Mark Hammond [:markh] [:mhammond]]

The current UX document has a couple of assumptions that will not be true with our current plan:

* It needs to reflect that the "soft-EOL" notifications will be the trigger for migration.  ie, the client isn't going to decide when to offer migration, but instead will be triggered once the sync servers send the notification.

* Given the above, self-hosted sync users really don't apply to this UX at all - their servers are not going to be sending the EOL notification.  I opened bug 1023076 for this, but in practice, it means self-hosted users shouldn't appear in the flowchat at all.

* Also given the above, the "if running legacy sync" item should be removed - only users running legacy sync will see this notification.

* Related, the flowchart talks about a generic "eol notification", but there are 2 classes of notification - "soft", which means sync is will working, and "hard" which means it is not.  This means the "Urgent upgrade notification" box doesn't really make sense - notifications will be "soft" (implying the "Gentle upgrade notification") or "hard" (implying the "Sync broken notification") but there is nothing in between that would take us to the "Urgent Upgrade Notification")

Comment 1

[Mark Hammond [:markh] [:mhammond]]

Current UX flows capture this.