Closed
Bug 1239786
Opened 10 years ago
Closed 9 years ago
Add deprecation/shutdown notice on https://login.persona.org
Categories
(Cloud Services :: Server: Identity, defect)
Cloud Services
Server: Identity
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rfkelly, Assigned: rfkelly)
Details
Attachments
(1 file)
Like Bug 1238848
| Assignee | ||
Comment 1•10 years ago
|
||
Dan says:
> https://login.persona.org/ is part of the main repo at https://github.com/mozilla/persona
Which IIRC is not running the latest branches from the repo in production. Based on Bug 1208480 I'm going to target a PR at branch (train-2014.07.19). However, https://login.persona.org/ver.txt says it's running version 4e9cea8, which I can't find as a commit in the repo. :relud can you confirm this is the right branch to target?
Flags: needinfo?(dthorn)
| Assignee | ||
Comment 2•10 years ago
|
||
Here's a shutdown notice variant for https://login.persona.org but I'm not sure it's worth it.
Unlike the other sites we've been adding this to, this is a *user* facing site. Users that wind up here, will do so because they're logging into site with persona, so I made this one a lot smaller. Still, there's not really anything they can do in response to the notice, except maybe bug the people who run the site they're signing into.
I suspect we don't really need this, and won't get a lot of value out of the hassle of redeploying the main persona codebase. But, am open to other opinions. Maybe we can consider adding it as we get closer to the shutdown?
Attachment #8708164 -
Flags: review?(dan.callahan)
Comment 3•10 years ago
|
||
+1 to reconsider once we're 6 months from shutdown (so, in May). Give folks time to migrate on their own, first.
Comment 4•10 years ago
|
||
that is the correct branch for the PR. the ver.txt doesn't match because the last deploy was built from a pull request. it will be correct later today.
Flags: needinfo?(dthorn)
Comment 5•10 years ago
|
||
ver.txt is correct now
| Assignee | ||
Comment 6•10 years ago
|
||
Interesting to note that some users are kind of expecting to see a deprecation warning as part of their login experience, e.g. https://twitter.com/tessarakt/status/688455242661392384
I don't think we should do that, certainly not yet, but I'm adding it here for context when we come to move forward on this again.
Comment 7•9 years ago
|
||
We're six months from shutdown -- should we reconsidered adding a deprecation notice to the user-facing website at https://login.persona.org?
I'm +1 on adding a visible notice.
Updated•9 years ago
|
Attachment #8708164 -
Flags: review?(dan.callahan) → review+
| Assignee | ||
Updated•9 years ago
|
Assignee: nobody → rfkelly
| Assignee | ||
Comment 8•9 years ago
|
||
Thanks Dan - yes, I think it's time for this. I will reach out to our internal reliers to check in on migration plans, and also let them know we'll be adding such a notice soon.
Comment 9•9 years ago
|
||
I need to deploy a puppet change today, and it would be easier to include this than not. Do you think it's okay to push this notice to prod today?
Flags: needinfo?(rfkelly)
Comment 10•9 years ago
|
||
I'm going to assume it's okay, since you wanted to do it over a month ago. Ping me if we should revert.
Flags: needinfo?(rfkelly)
| Assignee | ||
Comment 11•9 years ago
|
||
SGTM!
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•