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.
Created attachment 8669835 [details] placeholder-1211585 [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+
Al, do we need a sec-rating on this one and bug 1211586, 1211587? Thanks.
Not for this one because this is just a process bug.
status-b2g-v2.2: --- → affected
status-b2g-v2.2r: --- → affected
Attachment #8669835 - Flags: approval-mozilla-esr38? → approval-mozilla-esr38+
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.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
status-firefox-esr38: affected → fixed
Resolution: --- → FIXED
landed also on 2.2 and 2.2r like https://hg.mozilla.org/releases/mozilla-b2g37_v2_2r/rev/575e59560ad6
status-b2g-v2.2: affected → fixed
status-b2g-v2.2r: affected → fixed
Whiteboard: [post-critsmash-triage] → [post-critsmash-triage][adv-esr38.4-]
You need to log in before you can comment on or make changes to this bug.