Re-sign and re-test fake FF3.0.12, FF3.5.1 releases to verify new signing tools and machine

VERIFIED FIXED

Status

Release Engineering
General
VERIFIED FIXED
8 years ago
4 years ago

People

(Reporter: joduinn, Assigned: abillings)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Before we can roll the new keymaster into production, we need to verify that the machine, modified toolchain, and new scripts work as expected. 

In offline discussions at group gathering this week, we decided to re-sign the existing, known, FF3.0.12 and FF3.5.1 builds, and schedule with QA to get them properly tested. If all that goes ok, we can move new keymaster into production before the upcoming FF3.0.13 and FF3.5.2 releases.

In case it helps to reduce testing scope, the unsigned binaries will be identical. However, the signed binaries, and the update snippets will be different.

(Lets use this bug to track this project; catlee, once the builds are available, can you reassign this bug to abillings?)
Blocks: 470146
As per email yesterday, new builds are up at:

http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/experimental/newsigs/
Assignee: catlee → abillings
From email with abillings:
[snip]
Juan and I have tested these and we're done. We found no issues at  
all. Things look good.

We ran smoketests, did updates with uninstalls, and did some poking  
around.

Al
[snip]
Al: 

looks like this is now ok to close?
(Assignee)

Comment 4

8 years ago
Yes, I believe so.
(In reply to comment #3)
> Al: 
> 
> looks like this is now ok to close?


(In reply to comment #4)
> Yes, I believe so.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Assignee)

Comment 6

7 years ago
Marking verified forever later!
Status: RESOLVED → VERIFIED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.