Confirmed users
4,293
edits
No edit summary |
|||
| Line 1: | Line 1: | ||
For releases of Firefox and Thunderbird, the Build & Release team at Mozilla Corp uses a program called [http://mxr.mozilla.org/seamonkey/source/tools/patcher/ patcher2]. This document describes the basics of how to use it. | For releases of Firefox and Thunderbird, the Build & Release team at Mozilla Corp uses a program called [http://mxr.mozilla.org/seamonkey/source/tools/patcher/ patcher2]. This document describes the basics of how to use it. | ||
=Overview= | |||
==How Firefox/Thunderbird updates are tested== | |||
We use four update channels for Firefox & Thunderbird releases. The two channels that end users see are | |||
* beta - default channel for the releases 2.0a1, 2.0b1, and up to the last 2.0 beta | |||
* release - default channel for the first release candidate for 2.0. The vast majority of people are on this channel. | |||
Then there are | |||
* betatest - mainly QA testing of updates, pointing to the ftp server, to check that they apply properly, the UI works etc etc | |||
* releasetest - mainly QA testing of updates, pointing to download.m.o (bouncer), to make sure everything is available to end users when the release is imminent | |||
... | |||
=Define variables= | =Define variables= | ||
| Line 20: | Line 34: | ||
=Create/update config= | =Create/update config= | ||
=Make updates= | =Make updates= | ||