Closed
Bug 1211585
Opened 9 years ago
Closed 9 years ago
[meta] upgrade firefox 38 ESR to to nspr 4.10.10 and nss 3.19.2.1 on october 16 (release candidate first, final on october 19)
Categories
(Core :: Security: PSM, defect)
Tracking
()
People
(Reporter: KaiE, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta, sec-other, Whiteboard: [post-critsmash-triage][adv-esr38.4-])
Attachments
(1 file)
49 bytes,
text/plain
|
Sylvestre
:
approval-mozilla-esr38+
|
Details |
These NSPR and NSS upgrades are driven by the bugs listed in the dependency list, which are under embargo. We intend to land these patches into public NSS repository on October 15, and immediately afterwards into mozilla-inbound/central, for initial testing using the Firefox test automation. We should be ready to land release candidates of NSPR/NSS into the Firefox branch on October 16, and if it works fine, declare the final NSPR/NSS releases and land them into the Firefox branch by October 19. We're trying to land these patches as late as possible, but because you'll need time for Firefox release preparation, and testing of final Firefox builds, we're planning to do so two weeks prior to the scheduled November 3rd release date. Please let me know if this plan doesn't work for you.
Reporter | ||
Comment 1•9 years ago
|
||
[Approval Request Comment] fix critical security issues in NSPR and NSS Could you please approve by to October 15? Thank you.
Attachment #8669835 -
Flags: approval-mozilla-esr38?
Tracked for ESR 38.4.0
status-firefox-esr38:
--- → affected
tracking-firefox-esr38:
--- → 42+
Flags: needinfo?(abillings)
Al, do we need a sec-rating on this one and bug 1211586, 1211587? Thanks.
Comment 4•9 years ago
|
||
Not for this one because this is just a process bug.
Flags: needinfo?(abillings)
Updated•9 years ago
|
Updated•9 years ago
|
Group: crypto-core-security → core-security-release
Updated•9 years ago
|
status-b2g-v2.2:
--- → affected
status-b2g-v2.2r:
--- → affected
Updated•9 years ago
|
Attachment #8669835 -
Flags: approval-mozilla-esr38? → approval-mozilla-esr38+
Reporter | ||
Comment 5•9 years ago
|
||
https://hg.mozilla.org/releases/mozilla-esr38/rev/c9d2fbddfe40 Note these are release candidates. The final tags (plus the change to bump configure.in) are expected to land on Monday, hopefully without any code changes.
Reporter | ||
Comment 6•9 years ago
|
||
https://hg.mozilla.org/releases/mozilla-esr38/rev/44d784fdf614
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 7•9 years ago
|
||
landed also on 2.2 and 2.2r like https://hg.mozilla.org/releases/mozilla-b2g37_v2_2r/rev/575e59560ad6
Updated•9 years ago
|
Whiteboard: [post-critsmash-triage]
Updated•9 years ago
|
Whiteboard: [post-critsmash-triage] → [post-critsmash-triage][adv-esr38.4-]
Updated•8 years ago
|
Group: core-security-release
Updated•5 months ago
|
Blocks: nss-uplift
Updated•5 months ago
|
Summary: upgrade firefox 38 ESR to to nspr 4.10.10 and nss 3.19.2.1 on october 16 (release candidate first, final on october 19) → [meta] upgrade firefox 38 ESR to to nspr 4.10.10 and nss 3.19.2.1 on october 16 (release candidate first, final on october 19)
You need to log in
before you can comment on or make changes to this bug.
Description
•