Sign and dev deploy the Firefox update hotfix (v20140527.01) (v2)

RESOLVED FIXED

Status

Release Engineering
Releases
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: gps, Assigned: gps)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments, 2 obsolete attachments)

(Assignee)

Description

3 years ago
Created attachment 8450414 [details]
hotfix-v20140527.01.xpi

+++ This bug was initially created as a clone of Bug #1028388 +++

We have a new version of the hotfix that needs signing. It's attached.

Please sign and deploy to the dev/staging server like was done before.
Assignee: nobody → rail
Created attachment 8450454 [details]
hotfix-v20140527.01-signed.xpi
Feel free to resolve the bug when deployed.
This file has the same version number than the one that was previously uploaded. AMO doesn't handle this well, it requires a new version number.
argh, I'm doing something wrong... nthomas, halp! :)
Flags: needinfo?(nthomas)
I don't think you are. Previously we've had simpler hotfixes where QA in staging didn't hit any issues, but now we're iterating and hitting an AMO requirement we didn't know about before.

Jorge, are you referring to the version number in install.rdf, or the filename ?
Flags: needinfo?(nthomas) → needinfo?(jorge)
Looks like that may be the same thing, almost
 https://hg.mozilla.org/releases/firefox-hotfixes/file/fc3c622aff83/v20140527.01/install.rdf
The version number on install.rdf is what I care about, and I checked that it was the same as the one that was previously uploaded to AMO -dev.
Flags: needinfo?(jorge)
gps, please bump the version in install.rdf and attach a new xpi to sign.
Assignee: rail → gps
(Assignee)

Comment 9

3 years ago
Created attachment 8450630 [details]
hotfix-v20140527.01.xpi

I bumped the <em:version> to "20140527.01.1"

I hope this does the trick!

Will we need to do this in the final hotfix as well? Should I commit this source change?
Attachment #8450414 - Attachment is obsolete: true
Attachment #8450454 - Attachment is obsolete: true
(Assignee)

Updated

3 years ago
Assignee: gps → rail
(In reply to Gregory Szorc [:gps] from comment #9)
> Will we need to do this in the final hotfix as well? Should I commit this
> source change?

It's not necessary to do this for the final hotfix, since I haven't uploaded anything to production so far.
Created attachment 8450655 [details]
hotfix-v20140527.01-signed.xpi
Better to not change anything between staging QA and production though. Over to Jorge for upload.
Assignee: rail → jorge
Uploaded and published. Back to Rail.
Assignee: jorge → rail
Back to :gps, I'm not sure what are the next steps here.
Assignee: rail → gps
(Assignee)

Comment 15

3 years ago
If this is uploaded, there's nothing left to do except verify it works. I'll call this done.

Reopen if we can't install.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Assignee)

Comment 16

3 years ago
I was attempting to install the hotfix via the official hotfix deployment mechanism via the dev server. But I seem to be running into the issues described in bug 1031516.
(Assignee)

Comment 17

3 years ago
I tried installing the hotfix via the dev update server again today and can confirm it is working. You have to perform up to 3 background update checks before it gets pulled depending on what version of Firefox you are on. But it works.

My Firefox 12 install pulled v20121019.01, v20130826.01, and finally v20140527.01.1.
(Assignee)

Updated

3 years ago
Blocks: 1038382
You need to log in before you can comment on or make changes to this bug.