Releases/Firefox 6.0b6/BuildNotes
Notes About Releasing
Please update the Notes Template and the Release:Primer for future releases (bug fixes, changes to automation) as needed
Bugs hit
Enter any bugs pre-existing or newly discovered and filed during the release:
- bug - description
Build Engineers
{name} - Tracking bug: bug #
Signed-off Revision(s)
Build 1: #
L10N changesets
- Firefox: link to the l10n-changesets
- Fennec: link to the json
Tags
| Build # | Branch, Tags | Changeset |
| MOBILE60_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1 | # | |
| GECKO60_#_RELBRANCH, FIREFOX_VERSION_BUILD1 FIREFOX_VERSION_RELEASE | # |
Build data
Firefox
| Build # | Type | Build ID | Build machine | Time to build |
| 1 | Linux | |||
| Linux64 | ||||
| Mac | ||||
| Windows |
Fennec
| Build # | Type | Build ID | Build machine | Time to build |
| 1 | android | |||
| maemo5-gtk | ||||
| linux | ||||
| macosx | ||||
| win32 |
Notes
Build 1
E-mail Metrics
Tag
Bouncer Submitter
Source
Start autosign
Build
Firefox
Fennec
Android
Maemo5-GTK
Desktop Builds
Desktop repacks
Unittests / Talos
XULRunner
Source
Build
Signing
Repacks
Firefox
Fennec
Partner Repack
Firefox
Fennec
Firefox Signing
Android Signing
Android Signature Verification
Maemo5-GTK repos
L10N verify
Updates
Update verify
Major Update
Update verify
Socorro Product Data Updates
Check permissions / AV scan
Reset reserved slaves
Push files to internal mirrors
Push to beta
Push XULRunner to Mirrors
Update XULRunner wiki page
Publish Fennec
Create bouncer entry for maemo
Push the files
Publish to the Android Market
IMPORTANT - Apparently it is possible for the old apk to "come back from the dead" and on this release it turned out that a second visit to the (insert expletive here) Market was necessary to re-activate the 6.0b4 apk AGAIN. So watch your back with anything to do with the Market and check it twice.
PROTIP: after publishing new apk on android marketplace, ask anyone in RelEng who has an android device to check for updates. Some delay in seeing new apk might be caused by cache-needing-to-refresh. However, a multi-hour delay in seeing new apk means there is something wrong with the settings in marketplace website. Fixing this may require going to the "upload new apk" tab, then clicking the "advanced" tab and looking at the build ids to compare to the build date you're expecting.