442105 - Tracking bug for Build and Release of Major Update from FF2.0.0.16 to FF3.0.1

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P1)

Description

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

This bug is to track doing the *actual* major upgrade for real, and of rolling it out to endusers and beta testers.

Note: bug#394046 tracks the several test cycles done to verify that the FF2->FF3 major update process works for whenever we decide to do major update. Those test cycles are only for debugging the process and find any blocking bugs - they will never be seen by endusers or beta testers. See details in bug#394046.

Comment 2

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

Bringing over open blocker from bug 394046.

Comment 3

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

Notes to release engineer at the wheel for this:

* don't forget to change the channels in the patcher config (moz18-branch-major-update-patcher2.cfg) from
     channel = major
     testchannel = majortest
  to
     channel = beta release
     testchannel = betatest releasetest

* we need to generate empty snippets for the partner builds on their update channels, since we need to provide a custom update file and need to block them falling back to the beta/release channel. See https://intranet.mozilla.org/Release:_Firefox_1.5.0.12_to_2.0.0.4_Major_Update#Generate_null_partner_updates for pointers, Tomcat and Kev can provide information about the current list of channels.

Comment 4

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

(In reply to comment #3)

We'll also need to change the two values for url in moz18-branch-major-update-patcher2.cfg, so that we point at download.m.o.

Comment 5

[[e-mail] (:bhearsum)]

Re: null updates for partners.

I'm going to need a list of all of the partner update channels so I can generate null snippets for them.

Comment 6

[[e-mail] (:bhearsum)]

we're major updating against 3.0.1, removing blocking on 3.0.2

Comment 7

[[e-mail] (:bhearsum)]

Attachment: [checked in] update patcher config to generate real test+release snippets

As per Nick's comments we have to use the real channels (release/beta, releasetest/betatest) and update the URLs to point to bouncer.

Comment 8

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

Bug#357670 means we might not want to do major update for japanese mac. Waiting for final decision.

We have already created the major update snippets for all locales, including japanese mac, but we can easily delete at the last minute if thats the decision. Note: this would be a problem when updating to FF3.0.1 only, so another major update bringing people to FF3.0.2 can safely include japanese mac.

Comment 9

[[e-mail] (:bhearsum)]

Attachment: use 'releasetest' channel in update verify configs

Comment 10

[[e-mail] (:bhearsum)]

Comment on attachment 334465 [details] [diff] [review]
[checked in] update patcher config to generate real test+release snippets

Checking in moz18-branch-major-update-patcher2.cfg;
/cvsroot/mozilla/tools/patcher-configs/moz18-branch-major-update-patcher2.cfg,v  <--  moz18-branch-major-update-patcher2.cfg
new revision: 1.6; previous revision: 1.5
done

Comment 11

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

From email in release-drivers:

ja-JP-mac should *not* ship, on any beta/release channel. We will continue to ship japanese MU for win32, linux.

Comment 12

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

Pushed update snippets to beta channel Thursday evening (21st Aug 2008).

Comment 13

[[e-mail] (:bhearsum)]

shipped (yay!)

Comment 14

[Chris Cooper [:coop] (he/him)]

Moving closed Future bugs into Release Engineering in preparation for removing the Future component.