Closed Bug 1303370 Opened 8 years ago Closed 8 years ago

Update static pin expiration time for Fx 49 release before it ships

Categories

(Core :: Security: PSM, defect)

Product:
Core
Component:
Security: PSM
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla49
Tracking Flags:
Tracking Status
firefox49 blocking fixed
firefox50 --- unaffected
firefox51 --- unaffected

People

(Reporter: dveditz, Assigned: RyanVM)

Details

Since the static pins currently built into the 49 and 45.4 releases will expire before the next releases are planned we need to update the date from Nov 5 to something after Nov 8.

If we transplant the following changeset we'll get until 12-17 which buys us an extra cycle of time.

https://hg.mozilla.org/releases/mozilla-aurora/rev/66754db69a70


The above needs to land on mozilla-release and mozilla-esr45
Looks like ESR is already OK and we don't need to re-spin it:
https://hg.mozilla.org/releases/mozilla-esr45/rev/3c42249975a5

Doesn't matter which of those you transplant to mozilla-release they only differ by 31 seconds.
Keywords: checkin-needed
Summary: Update static pin expiration time for Fx 49/45.4 releases before they ship → Update static pin expiration time for Fx 49 release before it ships
https://hg.mozilla.org/releases/mozilla-release/rev/416dc3163a1f
Assignee: nobody → ryanvm
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox49: --- → fixed
status-firefox50: --- → unaffected
status-firefox51: --- → unaffected
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
Just marking this as a blocker after the fact. We are aiming to re-ship beta (RC4) today.
tracking-firefox49: --- → blocking
Keywords: checkin-needed
You need to log in before you can comment on or make changes to this bug.