We're a whiles away from being able to switch of sync1.1, but we've got plenty of work to do to move towards that goal. Here's a top-level metabug that we can hang related tasks off as they come up.

:rfelly Here is one of those bugs we were looking for last week and this.... We should tie it to the other Sync 1.5 migration meta bugs...

Adding Travis for context on blockers on decommissioning sync1.1 infra.

Passing this meta-bug over to Edwin, who is wrangling the cross-org details of the shutdown.

rfkelly - I'd assert that all bugs in this tree are resolved. Can you do a quick scan or we could have a triage session. I believe we had this concept of soft and hard EOL, but I think that feel out of scope and we just have the current notification message. We should do something thinking around what users experience when we turn off the servers -- that may not be captured.

The full set of possible messaging combinations are outlined here, including variants of hard-eol: https://bugzilla.mozilla.org/show_bug.cgi?id=1014411#c27 It's still an open question whether we want to go through the hard-eol phase, and I think we should decide it based on the profile of remaining active users on the service once the migration hits 100%.

I've cleared some of my bugs, and ni?'d some people to clear theirs. But it's probably valuable to do a quick triage at the next Sync standup, or perhaps before/after it if we don't want to drag the whole group in.

the decommission is complete