753006 - Please prepare automatic updates for FF3.6 to FF12

Status: RESOLVED FIXED

(Release Engineering :: Release Requests, defect)

Description

[Alex Keybl [:akeybl]]

Update type: Automatic
Updates from: Firefox 3.6.13 through 3.6.28
Updates to: Firefox 12.0
Update-to version in snippet: 12.0.0 (need the extra zero to overwrite users who clicked "No thanks" on the last MU)

Rollout:
* Let's go out with the 3.6.28->12.0 first and verify that everything is working as expected (or disable if not)
* Then let's roll out the rest (3.6.13-3.6.27->12.0)

Testing required:
* We need to test getting the old MU prompt on 3.6.28, declining it, and then receiving the automatic update
* We need to spot check 2 other update snippets from the 3.6.13-3.6.27 range (no MU testing required)

Comment 1

[Alex Keybl [:akeybl]]

When you guys (RelEng) have an ETA for when the snippets will be ready to push out, please let us know so that QA is prepared.

Comment 2

[[e-mail] (:bhearsum)]

I'll get these ready.

Comment 3

[[e-mail] (:bhearsum)]

do we need to change the detailsUrl? it's currently https://www.mozilla.org/af/firefox/unsupported/EOL

we can probably just copy & modify the existing snippets to save time

Comment 4

[[e-mail] (:bhearsum)]

I think we need to change the following:
updateType=major to updateType=minor

If Alex wants a different detailsUrl, that needs to be changed too.

Comment 5

[Alex Keybl [:akeybl]]

(In reply to Ben Hearsum [:bhearsum] from comment #4)
> I think we need to change the following:
> updateType=major to updateType=minor
> 
> If Alex wants a different detailsUrl, that needs to be changed too.

I don't believe the page linked to from the detailsUrl is ever prominently displayed to the user, but to be safe that link should be 

https://www.mozilla.org/firefox/unsupported/EOL

not

https://www.mozilla.org/af/firefox/unsupported/EOL

Thanks Ben!

Comment 6

[Rail Aliiev [:rail]]

# ffxbld@aus3-staging
cd /opt/aus2/snippets/staging
rsync -av Firefox-3.6.x-12.0-build1-MU-test/ Firefox-3.6.x-12.0-build1-minor-test/
rsync -av Firefox-3.6.x-12.0-build1-MU/ Firefox-3.6.x-12.0-build1-minor/


find Firefox-3.6.x-12.0-build1-minor-test Firefox-3.6.x-12.0-build1-minor -type f -exec sed -i -e 's,detailsUrl=.*,detailsUrl=https://www.mozilla.org/firefox/unsupported/EOL,g' -e 's,updateType=major,updateType=minor,g' {} \;

~/bin/backupsnip Firefox-3.6.x-12.0-build1-minor-test
~/bin/pushsnip Firefox-3.6.x-12.0-build1-minor-test


What means that the updates are live on the betatest and releasetest channels.

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

These snippets generate xml with extensionVersion="12.0.0" in them, the same as the major update to 12.0 we're replacing. But I've verified that both manual and background checks find the minor update after saying 'No Thanks' to the major one.

Comment 8

[u279076]

Just to confirm what I need to test:

 * Firefox 3.6.28 major update found > decline major update > automatic update to 12.0
 * Firefox 3.6.x manual update to 12.0
 * Firefox 3.6.x automatic update to 12.0

Comment 9

[Alex Keybl [:akeybl]]

(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #8)
> Just to confirm what I need to test:
> 
>  * Firefox 3.6.28 major update found > decline major update > automatic
> update to 12.0
>  * Firefox 3.6.x manual update to 12.0
>  * Firefox 3.6.x automatic update to 12.0

That's correct, but the decline major update part of the test needs to happen before we push the new auto updates live (although Nick's Comment 7 suggests everything is working fine).

Comment 10

[Nick Thomas [:nthomas] (UTC+12)]

My testing was
* check for updates on release channel, say 'No Thanks'. This creates a boolean pref app.update.never.12.0.0 with value true
* close firefox and swap to releasetest channel
* restart Firefox do manual check, or wait for background check with prefs tweaked to make that happen faster

Comment 11

[u279076]

Verified working on RELEASETEST using the following steps:
1. Install Firefox 3.6.28
2. Check for 12.0 Major Update on release channel
3. Click "no thanks"
4. Quit Firefox and set the channel to "releasetest"
5. Start Firefox and wait for background update
6. Restart and apply update
7. Verify running Firefox 12.0

IMO, we can push 3.6.28 -> 12.0 live.

Comment 12

[Nick Thomas [:nthomas] (UTC+12)]

Separate out 3.6.28 -> 12.0 on release:

cd /opt/aus2/snippets/staging/
mkdir -p Firefox-3.6.28-12.0-build1-minor/Firefox
mv Firefox-3.6.x-12.0-build1-minor/Firefox/3.6.28 Firefox-3.6.28-12.0-build1-minor/Firefox/

Comment 13

[Nick Thomas [:nthomas] (UTC+12)]

Firefox-3.6.28-12.0-build1-minor is pushed.

Comment 14

[u279076]

Firefox 3.6.28 -> 12.0 automatic background update verified on release channel.

Note: Due to timing, we will delay 3.6.13-27 -> 12.0 push until tomorrow morning. I'll test releasetest when I get to the office tomorrow morning and we can push soon after.

Comment 15

[u279076]

Firefox 3.6.13-27 -> 12.0 automatic background updates on releasetest channel look good. I think we can push these live.

Comment 16

[u279076]

Firefox 3.6.13-27 -> 12.0 automatic background updates on release channel look good. Did we want to keep this bug open to do 3.6.0-12 -> 12.0?

Comment 17

[Rail Aliiev [:rail]]

All done here

Comment 18

[Nick Thomas [:nthomas] (UTC+12)]

(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #16)
> Did we want to keep this bug open to do 3.6.0-12 -> 12.0?

We haven't been doing these versions because we can't distinguish PPC and Intel mac users. If there are significant numbers of Windows (and Linux hah!) users then we could do something platform specific for them.