515417 - do major update from Fx3.0x to Fx3.6x to make sure it all works

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[juan becerra [:juanb]]

We'll need major updates generated in order to test prior to the 3.6 release.

Comment 1

[Samuel Sidler (old account; do not CC)]

fwiw, this isn't all that "future". It needs to be done right after 3.6 beta 1 is built.

Comment 2

[juan becerra [:juanb]]

We need test updates generated from 3.0x and/or 3.5x to 3.6 before the next beta(3?) in order to have time to test it close to end-to-end.

Comment 3

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

Bug 515421 is higher priority than this.

Comment 4

[Samuel Sidler (old account; do not CC)]

(Well, we're going to have a major update on day 1 for sure. It's very unlikely we'll have a minor update on day 1. But for testing purposes, problems are more likely to be found with the minor update than the major one, so sure.)

Comment 5

[Mike Beltzner [:beltzner, not reading bugmail]]

Actually, I don't think this blocks. I'd *like* to have a major update available from 3.0 -> 3.6 on day one, but if that's the last bug we have to fix in order to ship, I don't think I'd hold ship for it, as sad as it would make me.

This won't require code changes in 3.6, AIUI, so I can't really block on it, though I'd obviously like to see it happen. If you feel like I'm not thinking this through the right way, please renominate.

Comment 6

[Samuel Sidler (old account; do not CC)]

(In reply to comment #5)
> This won't require code changes in 3.6, AIUI, so I can't really block on it,
> though I'd obviously like to see it happen. If you feel like I'm not thinking
> this through the right way, please renominate.

It might require code changes if QA finds issues in migration...

Comment 7

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

Attachment: Patcher config for 3.0.15 -> 3.6b2

Comment 8

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

Attachment: Update verify config for 3.0.15 -> 3.6b2

This is against rev fe36680c2170, but it should work until we do another 3.0.x to 3.5.y major update.

Comment 9

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

Attachment: Patcher config for 3.0.15 -> 3.6b4

Comment 10

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

Attachment: Update verify config for 3.0.15 -> 3.6b4

Comment 11

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

3.0.15 -> 3.6b2 is ready for testing by QA.

Comment 12

[juan becerra [:juanb]]

Please re-enable this on a testing channel.

Comment 13

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

(In reply to comment #12)
> Please re-enable this on a testing channel.

3.0.15 -> 3.6b4 has been moved to the "majortest" channel.

Comment 14

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

juanb: any news on this?

(From comment#5 I note its "nice to have but blocking-" for FF3.6. However, not sure how close it is to being done so adding dep bugs just in case its almost ready.)

Comment 15

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

I'm going to refresh this MU to 3.0.17 -> 3.6rc1 build1 tomorrow.

Comment 16

[Mike Beltzner [:beltzner, not reading bugmail]]

Thanks, Nick. Once that's done, please notify release-drivers and we can figure out a QA path. I'd really like to have that major update available for the day that we launch, if possible.

Comment 17

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

Attachment: Patcher config for 3.0.17 -> 3.6rc1

Comment 18

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

Attachment: Update verify config for 3.0.17 -> 3.6rc1

Comment 19

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

Attachment: Update verify config for 3.0.17 -> 3.6rc1

Fixes channel.

Comment 20

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

Attachment: Patcher config for 3.0.17 -> 3.6rc2

Comment 21

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

Might we still do 3.0.x -> 3.6 updates ? The 3.0.17 -> 3.6rc2 path is currently available for testing on majortest.

Comment 22

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

From today's firefox release meeting, tchung thinks QA *might* be able to get this tested in "a few days", but will get back to us.

Comment 23

[Tony Chung [:tchung]]

(In reply to comment #22)
> From today's firefox release meeting, tchung thinks QA *might* be able to get
> this tested in "a few days", but will get back to us.

Correction, that comment was made by Juan today, not me.  However, we ran similar tests to 3.5.7 -> 3.6b2 for windows/mac/linux, and iirc- it took around 3 days.

Comment 24

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to comment #23)
> (In reply to comment #22)
> > From today's firefox release meeting, tchung thinks QA *might* be able to get
> > this tested in "a few days", but will get back to us.
> 
> Correction, that comment was made by Juan today, not me.  
Ah, sorry, my bad. I since talked with juanb today about this, he thinks tests should be done by early next week, but will keep us posted.

> However, we ran
> similar tests to 3.5.7 -> 3.6b2 for windows/mac/linux, and iirc- it took around
> 3 days.
ok, thanks.

Comment 25

[juan becerra [:juanb]]

Results are consistent with 3.5.7->3.6: https://wiki.mozilla.org/Releases/firefox_3.6RC2/Test_Plan:Major_Updates

We can see bug 542391 in this iteration as well, but other than that the other results are passing.

Comment 26

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

QA has signed off, we'll do this for real for 3.0.18 -> 3.6 in bug 543853.