Closed Bug 811039 Opened 12 years ago Closed 12 years ago

Persona: Deploy train-2012.11.09 to staging environment

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Product:
Cloud Services
Component:
Operations: Deployment Requests - DEPRECATED
Platform:
x86
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jrgm, Assigned: gene)

References

Details

Please deploy train-2012.11.09.1 to the staging environment.

(NOTE: this train requires node.js 0.8.12)

sha: 8d18873
No longer depends on: 806474, 807127, 807129
Bah. Correction. The sha is 3cfa4d1 for train-2012.11.09 branch.
Starting work
staging is updated. still working on clientN
Status: NEW → ASSIGNED
clientN and l10n are updated.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Thanks Gene. I've confirmed /ver.txt has the right sha, all node processes are restarted and not flapping, and a quick pass in usage works fine. So I'm good to go.
Status: RESOLVED → VERIFIED
Assignee: nobody → gene
Gene: can you please respin the rpm to pick up latest l10n content and then deploy that onto stage so I can give it a brief sanity check?
New l10n info deployed to stage, clientN and l10n

browserid-server-0.2012.11.09-2.el6_110770.x86_64
Status: VERIFIED → RESOLVED
Closed: 12 years ago → 12 years ago
I've run a basic check and a script to pop the dialog an main site in the supported langs, and it looks good to me.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.