Richard Newman [:rnewman] Reporter
	Description • 11 years ago

+++ This bug was initially created as a clone of Bug #895518 +++

We'll need to notify users of partitioning when they upgrade Sync to Sync.next.

16 months ago I started a discussion around this. Here's a fragment of my email.

---
* landing strings to report a protocol upgrade
* changing wording to be aware of two different setup processes for "Firefox Sync" and "Foxfire BIDSink", which will unfortunately have exactly the same name. (We can't assume that a user will have Firefox 16 on all of their devices.)
* implementing detection code by...
** extending or using the meta/global storage version logic to allow the new client to leave a 'marker' in the 1.1/v5 account;
** setting some other record in 'meta';
** annotating some client record field with a protocol version;
** allowing an account to be marked as obsolete post-upgrade, with a server response that Firefox 14 clients can use to detect their obsolescence.
---

	Richard Newman [:rnewman] Reporter
	Comment 1 • 11 years ago

Need to be considerate of downgrade here, too.

	James Bonacci [:jbonacci]
	Comment 2 • 11 years ago

(it's weird that we have two bugs with the same title, one blocking the other....)

REMINDER for Deb, Tauni - 
we need to add this to our "user stories" Bugzilla dependency tree...

	Richard Newman [:rnewman] Reporter
	Comment 3 • 11 years ago

(In reply to James Bonacci [:jbonacci] from comment #2)
> (it's weird that we have two bugs with the same title, one blocking the
> other....)

I trust people to look at the Component :P

	James Bonacci [:jbonacci]
	Comment 4 • 11 years ago

Well *some* people need to pay more attention to that I guess... ;-)

	Richard Newman [:rnewman] Reporter
	Comment 5 • 11 years ago

Underway:

https://github.com/mozilla-services/android-sync/pull/374

	Richard Newman [:rnewman] Reporter
	Comment 6 • 11 years ago

Interestingly, we already support 400 Bad Request [16] => Upgrade Required.

http://docs.services.mozilla.com/respcodes.html#respcodes

It doesn't display a UI, but it's a good option for locking out older clients. We can set up a Zeus rule to send that to old UAs, and newer protocol deprecation indicators to the rest.

	Richard Newman [:rnewman] Reporter
	Comment 7 • 11 years ago

Hah. I can't believe I thought of this *two years ago*.

Bug 714304 covers the minimal version. This bug will be to (a) match desktop, and (b) display UI.

	Richard Newman [:rnewman] Reporter
	Comment 8 • 11 years ago

This is probably ready for review; I don't remember! So f? for now.

	Nick Alexander :nalexander [he/him] (PTO until Montreallhands August 21, 2023)
	Comment 9 • 11 years ago

I feel like this might be slipping through the cracks.  It looks like it would need another pass before landing, at least.  Status?

	Richard Newman [:rnewman] Reporter
	Comment 10 • 10 years ago

I won't have time to finish this off.

	Ryan Kelly [:rfkelly]
	Comment 11 • 9 years ago

IIUC the migration work is as done as it's going to get; closing out the bugs for completeness