Releases/Firefox 4.0/BuildNotes

Release Engineers

bhearsum, nthomas, jhford

Tracking Bug

bug 642234

Notes

Notify Mirrors

Joduinn sent this on March 16th.

Config Update

This small update to the release config was landed.

Automated Parts

Some of this release-day work makes sense to do from the release automation. Use force build for these.

Tag

modified release config [buildbot-configs@0781df67af87]

forced build using the webform with values

your name: jhford
reason for build: retagging for 4.0 release
branch to build: <left blank>
revision to build: <left blank>
repository to build: <left blank>
project to build: <left blank>
prop1 name: script_repo_revision
     value: FIREFOX_4_0_RELEASE
prop2 name: release_config
     value: mozilla/release-firefox-mozilla-2.0.py

Virus Scan

(Might not be able to do this from automation because we don't have a full 3.6-candidates dir)

Verify permissions

(Might not be able to do this from automation because we don't have a full 3.6-candidates dir)

Stage and Rename Files

Summary:

• Copy files to ~ffxbld and rename to non-RC versions
  • Exclude *checksums* because we don't care for individual locale+platform checksums files in the final release dir
  • Exclude partial MARs because there's no use for them, no point in pushing them to the mirrors
  • Exclude Source packages because they're regenerated for final
  • Exclude *SUMS* because we'll be regenerating them.

Details:

# ffxbld@stage
mkdir firefox-4.0
cd firefox-4.0
rsync -av --exclude=*checksums* --exclude='*partial.mar' --exclude=source --exclude=*SUMS* /pub/mozilla.org/firefox/releases/4.0rc1/ .

Index Files

todo: ask justdave how far in advance we should put an index.html in place

Notify AV Vendors

Need to notify AV vendors after the push to mirrors is done so that they can scan the files.

Update symlinks on FTP

To be done

ln -s 4.0 latest-4.0  
ln -s latest-4.0 latest

XULRunner

No need to stage or rename files because the 2.0rc1 versions already use "2.0".