Closed Bug 1049006 Opened 10 years ago Closed 10 years ago

Update Mozilla 33 to use NSS 3.17 final and NSPR 4.10.7 final

Categories

(Core :: Security: PSM, defect)

33 Branch
defect
Not set
blocker

Tracking

()

VERIFIED FIXED
mozilla34
Tracking Status
firefox33 + verified
firefox34 --- verified

People

(Reporter: KaiE, Assigned: KaiE)

Details

Attachments

(1 file)

This bug is for landing NSS 3.17 beta and RTM tags into mozilla-aurora (FF33) and mozilla-central (FF34).

FF33 already uses 3.17 beta, so it's required to upgrade it to the final version, we should get that done prior to the next FF branch merge date, around the end of august.
Version: 32 Branch → 33 Branch
Wan-Teh, do you agree with landing a new beta snapshot of NSS trunk into mozilla-inbound today? If you agree, I will take care of it.
Kai: yes, I agree. Give me 60 minutes because I still have two patches
to land.
updated to NSS_3_17_BETA2
https://hg.mozilla.org/integration/mozilla-inbound/rev/07b8619be3bb
Whiteboard: [leave open]
I'm extending the scope of this bug to cover NSPR, too, because Firefox 33 currently uses beta versions for both.

In the meantime both final RTM versions have been produced.
Summary: Update Mozilla 33 to use NSS 3.17 final (once it's ready) → Update Mozilla 33 to use NSS 3.17 final and NSPR 4.10.7 final
Attached file update instructions
Wan-Teh, do you agree?
Attachment #8472333 - Flags: review?(wtc)
Attachment #8472333 - Flags: approval-mozilla-aurora?
[Tracking Requested - why for this release]:

Because we must not ship beta versions of included libraries with Firefox releases, we must upgrade the branch to release versions.
OK. Any ETA for the stable releases?
Comment on attachment 8472333 [details]
update instructions

r=wtc. Thanks.
Attachment #8472333 - Flags: review?(wtc) → review+
(In reply to Sylvestre Ledru [:sylvestre] from comment #8)
> OK. Any ETA for the stable releases?

thanks, they're already released, I could land immediately, and I'll try to watch for open trees...
Comment on attachment 8472333 [details]
update instructions

clearing approval request. I understand the tracking flag on this bug is equivalent to a branch approval.
Attachment #8472333 - Flags: approval-mozilla-aurora?
https://hg.mozilla.org/integration/mozilla-inbound/rev/32ac8061e886
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [leave open]
reopening, because it landed on inbound, not m-c yet
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
https://hg.mozilla.org/mozilla-central/rev/32ac8061e886
Assignee: nobody → kaie
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Flags: qe-verify+
QA Contact: kamiljoz
Quickly talked to Kai via IRC and he mentioned that there wasn't any functionally to test here.. Suggested going through the tag info/commits to make sure that the new versions have been landed:

Went through the tag info under aurora and ensured that:
- NSPR_4_10_7_BETA3 -> NSPR_4_10_7_RTM
- NSS_3_17_BETA1 -> NSS_3_17_RTM

Went through some of the aurora commits in comment #13 and it appears like the new versions have been added

Double checked using MXR:
- http://mxr.mozilla.org/mozilla-aurora/source/nsprpub/TAG-INFO#1 (NSPR_4_10_7_RTM)
- http://mxr.mozilla.org/mozilla-aurora/source/security/nss/TAG-INFO#1 (NSS_3_17_RTM)

Went through the tag info under m-c and ensured that:

- NSPR_4_10_7_BETA3 -> NSPR_4_10_7_RTM
- NSS_3_17_BETA1 -> NSS_3_17_RTM

Went through some of the m-c commits in comment #15 and it appears like the new versions have been added

Double checked using MXR:
- http://mxr.mozilla.org/mozilla-central/source/nsprpub/TAG-INFO#1
- http://mxr.mozilla.org/mozilla-central/source/security/nss/TAG-INFO#1
Status: RESOLVED → VERIFIED
FYI for next time, configure.in also needs to have a version bump (for --with-system-nss). See bug 1053565.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: