636533 - do another major update offer from 3.6 to 4.0 for testing purposes

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[juan becerra [:juanb]]

QA needs another MU offer for testing purposes.

Comment 1

[LegNeato]

Errr, can't we just modify existing snippets and point the updater locally?

Comment 2

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

We need to get the updated generation up anyway, so this is just a push in that direction.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Next Friday we will have an Add-ons testday and I would really like to make MU tests part of it. Would be great if we can have major update snippets available by that day.

Comment 4

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

per irc, whimboo means March 4th, which should be no problem.

Comment 5

[LegNeato]

Honestly, I don't think this will block the release. We know that MUs work and can test with some hackery if needed. Additionally, there is nothing here that needs to land in the tree and can get fixed whenever.

Comment 6

[Josh Aas]

Clearing the hardblocker flag since this has blocking2.0-.

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

How does the 3.6.14/15 respin affect our major updates to Firefox 4? As part of our testday tomorrow we wanted to exercise major update scenarios. Nothing happened on this bug in the last week. I wonder if we can proceed with our goal or if we should drop it because no MU will be available.

Comment 8

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

I'm planning to work on it today, assuming I'm not tied up with 3.6.15 or 4.0rc1. Given we've suspended updates to 3.6.14 and < 10% of 3.6.13 users have updated, and 4.0rc is only just getting started, I'm intending to connect 3.6.13 -> 4.0b12. Does that sound OK ?

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Yes, that would be perfect. Please update this bug with more information. Once it is available I will update our testday documentation. Thanks.

Comment 10

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

On track to have this up in a few hours. It'll be the majortest channel, for any of 3.6.13, 3.6.14, or 3.6.15 (since it's likely 3.6.15 will come out complicate things).

Comment 11

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

whimboo: take a release build of 3.6.13 or 3.6.14, or 3.6.15 after that's shipped, set the channel to 'majortest' [1] and Help > Check for Updates. 4.0b12 will get sucked off the mirrors. Only i386 Mac gets offered the update, in the unlikely you someone with ppc turns up. 3.6.x updates are throttled, but everyone will be doing Help > Check for Updates so it won't matter.

[1] Two ways to switch the channel, both permanent
*) modify <install dir>/defaults/prefs/channel-prefs.js with a text editor, restart Firefox if it's running. Change 'release' or 'beta' to 'majortest'.
*) in about:config
   right click, make a new pref, of type string, 
     named: app.update.url.override
     value: https://aus2.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/majortest/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml

The second method doesn't require a restart. 

-----
RelEng details:
Snippet dir is 20110303-Firefox-3.6.13_14_15-4.0b12-MU-test, generated on a staging master with a bunch of patches, and some manual hacking afterwards to get 3.6.14 and 3.6.15 too, for shame. The billboard is hosted at http://people.mozilla.com/~nthomas/mu/index.html, but is roughly the content bug 633060 will deliver.

Comment 12

[Tracy Walker [:tracy]]

Nick, I assume this can be kept on as long as needed.  On MU, Sync is going to be pulling some shenanigans with the 1.7 extension versus the built version of Sync. So I'll need this to stay active at least until a dev. version of Sync 1.7 is available.

Comment 13

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

The majortest channel won't get overwritten by any releases that come along, so we'll be fine as long as 4.0b12 remains good for your testing. We have a bug to get the generation of major updates automated so that refreshing the MU is quick and easy.

Comment 14

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

Tracy, can I remove the 3.6.13/14/15 -> 4.0b12 MU now that we have a 3.5.17/3.6.15 -> 4.0rc1 up ?

Comment 15

[Tracy Walker [:tracy]]

(In reply to comment #14)
> Tracy, can I remove the 3.6.13/14/15 -> 4.0b12 MU now that we have a
> 3.5.17/3.6.15 -> 4.0rc1 up ?

Nick, yes, thank you. :-)

Comment 16

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

All cleaned up in both MPT + PHX:

cd /opt/aus2/incoming/3/Firefox
find 3.6.1{3,4,5}/ -depth -name majortest -type d -print -exec rm -rf {} \;