Releases/Firefox 2.0.0.16:BuildNotes

From MozillaWiki
Jump to navigation Jump to search

Build Engineers

bhearsum
Version/config bump bug

Bonsai queries

Build 1: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=AviarySuiteBranchTinderbox&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-07-02+01%3A49+PDT&maxdate=2008-07-02+01%3A51+PDT&cvsroot=%2Fcvsroot

Tags

Updated CVS Tags devmo page.

Build 1:

Module Branch Tag Pull date
cvsroot/mozilla MOZILLA_1_8_BRANCH FIREFOX_2_0_0_16_BUILD1 2008-07-02 02:13 PDT
l10n/l10n MOZILLA_1_8_BRANCH FIREFOX_2_0_0_16_BUILD1 2008-07-02 02:13 PDT

Build data

Type Build ID SHA1 Push date Build machine
[Windows installer/zip] 2008070205 production-pacifica-vm
[Mac compressed] 2008070205 bm-xserve05
[Linux compressed] 2008070204 production-prometheus-vm

Notes

Build 1

Bootstrap tag: RELEASE_AUTOMATION_M10 Setup before starting:

  • Updated /builds/buildbot/Automation/buildbot-configs on production-1.8-master.
    • master.cfg is "Locally Modified" to contain passwords. Identical to repository version otherwise.
    • Turned off the nightly builders on production-1.8-master to make sure they don't interfere with the release. (We need to figure out how to avoid this in the future).
    • update mozilla1.8 tinderbox to say "no nightlies right now"
    • Ran 'buildbot reconfig'
  • update /builds/tinderbox/mozilla/tools/tinderbox to the Bootstrap tag (need to revert this before restarting nightlies)
    • Had to tag this first. It was missed when RELEASE_AUTOMATION_M10 was created.
  • ensure that machines have enough resources
    • production-prometheus-vm - 32G on /
    • production-1.8-master - 11G on /builds, 4G on /data
    • production-pacifica-vm - 33.4G on c:
    • bm-xserve05 - 32G on /

Tag

Automated, no problems.

Source

Automated, no problems.

Build

Automated, no problems.

Repack

No problems

Sign

  • Signing doc
  • Accidentally ran 'find . -size +10000 -exec rm {} \;' in ~/signing-work while signing 2.0.0.16. This command deleted a ton of old builds, and broke the 2.0.0.16 signing. Had to restart signing from the beginning.

L10nVerify

Generate Updates

Publish Updates to Test Channels (betatest & releasetest)

Update Verify

Stage

Push Updates to Beta Channels

Sign Installers

Update Bouncer

Push to mirrors

Final Verification

Publish Updates to Release Channel

Release

Free Software Builds