Closed Bug 715183 Opened 11 years ago Closed 10 years ago

BrowserID: Get Production running latest node and npm

Categories

(Cloud Services :: Operations: Miscellaneous, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jbonacci, Assigned: petef)

Details

(Whiteboard: [qa+])

We need to get Production, load gen clients, and Stage all running the latest, known good versions of node and npm.

Tested and usable:
node v0.6.5 and npm 1.1.0-alpha-6

Not fully tested:
node v0.6.6 plus npm (what version?)

I am voting for v0.6.5 because I ran into issues attempting a local install of v0.6.6.

Source:
http://nodejs.org/dist/
Example: http://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz
Whiteboard: [qa+]
we may want to hold off for node v0.6.7. I hear it's going to have a bug-fix against that hash-collision DoS.

FYI, we should do this upgrade on an "off-day" -- not the same day we do trains (minimize amount of changes in prod at once).
Assignee: nobody → petef
(In reply to Pete Fritchman [:petef] from comment #1)
> we may want to hold off for node v0.6.7. I hear it's going to have a bug-fix
> against that hash-collision DoS.

http://groups.google.com/group/nodejs/msg/760724ad90b27f25
Dec 30: "Hang tight. v0.6.7 is coming up soon."

http://groups.google.com/group/nodejs/msg/731d9be4d3931cea
Jan 3: "next day or two"
The current train in stage is running against nodejs 0.6.10.
Status: NEW → ASSIGNED
Yes it is! Should we mark this as Resolved/Fixed or are you holding for PHX?...
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.