Closed Bug 1008066 Opened 11 years ago Closed 9 years ago

[meta] prepare for decommissioning of sync1.1 infrastructure

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rfkelly, Assigned: edwong)

References

Details

(Whiteboard: [qa+])

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.
Depends on: migratesync
Whiteboard: [qa+]
Depends on: 908463
: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...
Assignee: nobody → rfkelly
Status: NEW → ASSIGNED
Adding Travis for context on blockers on decommissioning sync1.1 infra.
Depends on: 1110013
Depends on: 1118108
Passing this meta-bug over to Edwin, who is wrangling the cross-org details of the shutdown.
Assignee: rfkelly → edwong
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.
Depends on: 1194030
Depends on: 1207867
the decommission is complete
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
No longer depends on: 957845
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.