Closed
Bug 487521
Opened 17 years ago
Closed 17 years ago
Do Firefox major update from 2.0.0.20 to 3.0.10
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
()
Details
Attachments
(2 files)
|
7.04 KB,
patch
|
bhearsum
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
|
7.05 KB,
patch
|
bhearsum
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
Assuming this is going to get tested while 3.0.9 is on the beta channel. Waiting on buildID's for 3.0.9 build 2 at this point.
| Assignee | ||
Updated•17 years ago
|
Priority: -- → P2
| Assignee | ||
Comment 1•17 years ago
|
||
No changes in locale list between 3.0.5 and 3.0.9, and the start point of 2.0.0.20 is unchanged, so this is mostly s/3.0.5/3.0.9/ and updated buildIDs. The quirk is that we're working from the candidate builds for now, so I added betatest-url. Using those candidates for update verify too.
We're scheduled to go to beta for the major update on the same day as 3.0.9 is released (Apr 22) so I didn't add a beta-url and we'll use bouncer there.
Attachment #372497 -
Flags: review?(bhearsum)
Comment 2•17 years ago
|
||
Comment on attachment 372497 [details] [diff] [review]
Patcher and verify config for 2.0.0.20 --> 3.0.9
Looks good to me.
Attachment #372497 -
Flags: review?(bhearsum) → review+
| Assignee | ||
Updated•17 years ago
|
Attachment #372497 -
Flags: checked‑in+
| Assignee | ||
Comment 3•17 years ago
|
||
Comment on attachment 372497 [details] [diff] [review]
Patcher and verify config for 2.0.0.20 --> 3.0.9
/cvsroot/mozilla/tools/patcher-configs/moz18-branch-major-update-patcher2.cfg,v <-- moz18-branch-major-update-patcher2.cfg
new revision: 1.11; previous revision: 1.10
and committed changeset 267:be58c41fca2b
| Assignee | ||
Comment 4•17 years ago
|
||
Updates are available on betatest for testing, pointing at the 3.0.9-candidates/build2 directory on the ftp server.
| Assignee | ||
Comment 5•17 years ago
|
||
We went to the beta channel with 3.0.9 then had to firedrill 3.0.10 for a topcrasher. We'll now regenerate the MU to connect 2.0.0.20 to 3.0.10 - morphing bug summary to match.
Summary: Do Firefox major update from 2.0.0.20 to 3.0.9 → Do Firefox major update from 2.0.0.20 to 3.0.10
| Assignee | ||
Updated•17 years ago
|
Attachment #372497 -
Attachment description: Patcher config for 2.0.0.20 --> 3.0.9 → Patcher and verify config for 2.0.0.20 --> 3.0.9
| Assignee | ||
Comment 6•17 years ago
|
||
Swaps back to release copies of files, removes betatest-url so that all channels go via bouncer, the usual version and buildid bumps.
Attachment #375978 -
Flags: review?(bhearsum)
Comment 7•17 years ago
|
||
Comment on attachment 375978 [details] [diff] [review]
Patcher and verify config for 2.0.0.20 --> 3.0.10
Looks good to me
Attachment #375978 -
Flags: review?(bhearsum) → review+
| Assignee | ||
Comment 8•17 years ago
|
||
Comment on attachment 375978 [details] [diff] [review]
Patcher and verify config for 2.0.0.20 --> 3.0.10
Checking in moz18-branch-major-update-patcher2.cfg;
new revision: 1.12; previous revision: 1.11
and
http://hg.mozilla.org/build/tools/rev/3728b8e79238
Attachment #375978 -
Flags: checked‑in+
| Assignee | ||
Comment 9•17 years ago
|
||
Updates are available on betatest for testing, pointing at the
3.0.10 update files on the mirrors.
| Assignee | ||
Comment 10•17 years ago
|
||
Shipped today.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•