Closed Bug 908463 Opened 11 years ago Closed 9 years ago

Ensure link sent in Sync EOL headers is appropriate for migration.

Categories

(Firefox :: Sync, defect)

defect
Not set
normal
Points:
5

Tracking

()

RESOLVED FIXED

People

(Reporter: rnewman, Unassigned)

References

Details

B. Your account has been upgraded, and you're no longer syncing. 3. … and you're on a pre-FxA device: "Your Firefox is no longer syncing. You might need to update your Firefox. [Learn more]."
Summary: Storage deprecation indicator (pre-FxA) → Storage deprecation indicator (pre-FxA): desktop client support
Blocks: 908465
Blocks: 905997
Blocks: 1008066
Flags: firefox-backlog+
Whiteboard: [qa+] → [qa+] p=5
This bug is for the case when an EOL notification is received by the server, but the Firefox version isn't "migration aware" - eg, 29, which is FxA enabled, but has no explicit support for a semi-automated migration. In this case, we will display the existing infobar, with a link to the "learn more" page. Bug 908467 is for the services team to send the notification, so this bug is really just for the creation of that "learn more" page so the sync servers can send that URL along with the EOL notification.
Blocks: 908467
Summary: Storage deprecation indicator (pre-FxA): desktop client support → Messaging for sync deprecation, pre-migration-aware desktop client support
Doh! (In reply to Mark Hammond [:markh] from comment #1) > This bug is for the case when an EOL notification is received by the server, ... received *from* the server
Points: --- → 5
Flags: qe-verify+
Whiteboard: [qa+] p=5
Bob, can you please confirm that the link sent with the EOL headers is appropriate for migration - ie, that it explicitly mentions the migration/upgrade? We want this so old clients that aren't migration aware see something reasonable. FWIW, a migration-aware client will refer the user to https://support.mozilla.org/en-US/kb/firefox-sync-upgrade-frequently-asked-questions, so if you don't already have a good URL, that might be a good option (although localization etc may make that tricky). If everything is good, please just close this bug.
Flags: needinfo?(bobm)
Summary: Messaging for sync deprecation, pre-migration-aware desktop client support → Ensure link sent in Sync EOL headers is appropriate for migration.
(In reply to Mark Hammond [:markh] from comment #3) > Bob, can you please confirm that the link sent with the EOL headers is > appropriate for migration - ie, that it explicitly mentions the > migration/upgrade? We want this so old clients that aren't migration aware > see something reasonable. > > FWIW, a migration-aware client will refer the user to > https://support.mozilla.org/en-US/kb/firefox-sync-upgrade-frequently-asked- > questions, so if you don't already have a good URL, that might be a good > option (although localization etc may make that tricky). > > If everything is good, please just close this bug. The present EOL link is: https://blog.mozilla.org/services/2015/02/03/legacy-sync-migration/ It mentions most of all the right things, but SUMO is probably a better place for people in search of help. Happy to switch the link to the SUMO link included here if the responsible parties give it a thumbs up. So let me start: +1 from operations.
Flags: needinfo?(bobm)
sumo :thumbsup:
I'll pretend I can speak for desktop, especially given desktop already points there ;) So +1
Actually, I should be clear - desktop *actually* points at: https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/sync-upgrade, which, on current DevEdition, "resolves" to https://support.mozilla.org/1/firefox/40.0a2/WINNT/en-US/sync-upgrade, which redirects to the link above. This may be important if the content has been translated into other languages. I'm not sure how important that is in this context, or even if you have any of that information available at the time you need to build the URL.
> if you have any of that information available at the time you need to build the URL. We could probably take a good guess at it, but that's additional code we'd have to write and deploy to the servers. Going to https://support.mozilla.org/kb/firefox-sync-upgrade-frequently-asked-questions (i.e. without the "en-US" part in the URL) at least seems to properly redirect based on language preferences, and I think that's sufficient.
SGTM - let's make it so!
Made so. Closing bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.