Closed Bug 865828 Opened 7 years ago Closed 6 years ago
Upgrade Mozilla 23 to NSPR 4
.10 (once it's ready)
From now on in the future, I propose that a tracking bug is filed, whenever you start upgrading mozilla to a newer version of NSPR - because in the past, it was regularly forgotten to keep things in shape, by eventually upgrading the affected mozilla branch to the final version of that nspr (or nss) version. Today Wan-Teh sugested to upgrade mozilla-central to NSPR 4.10 beta1. I'm willing to help out with this initial push, but I'm unwilling to be the one who tracks that the mozilla branch will be kept in shape. Let's use this tracking bug. As mozilla-central is currently equivalent to Mozilla 23, I'm setting the 23 branch as the affected and target version. I'm adding [leave open] to the status whiteboard, to indicate that the bug should be kept open after beta landings. Please remove that status whiteboard entry after you have landed the final NSPR release (once it's ready). I don't know to whom this bug should be assigned to.
Wan-Teh gave me r=wtc for landing the NSPR_4_10_BETA1 snapshot into mozilla-central. I believe this is the first time that anyone is using the modified client.py script to import an NSPR snapshot into mozilla-central. So if things break, don't blame me, but back out and find the person who did the script.
NSPR_4_10_BETA2 pushed to mozilla-inbound: https://hg.mozilla.org/integration/mozilla-inbound/rev/24997e3446b1
Assignee: nobody → wtc
Status: NEW → ASSIGNED
Priority: -- → P1
Fwiw, it seems 23 (now in mozilla-release) ships with nspr 4.10, but configure.in checks for 4.9.6, and this bug wasnt fixed/closed when it was updated from the betas to the RTM version in bug 858231. So i think this one can be closed now ? oh, and in all branches configure.in checks for nspr 4.9.6 when building with systemwide nspr, but we dont really care since it also checks for nss 3.15 which depends on nspr 4.10. Could only affect people trying to build with bundled nss & systemwide nspr 4.9.6, i doubt anyone cares...
Tip is running 4.10.4 beta2. Not sure why this bug is still open.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.