Releases/Firefox 4.0/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 70: Line 70:
"force build" source builder
"force build" source builder
==== Major Update Generation ====
==== Major Update Generation ====
'''not done yet'''
manually modify 3.5 -> 3.6rc2build3 and 3.6 -> 3.6rc2build3 snippets to point at non-RC bouncer links, and have non-RC2 appv's.


==== Bouncer Entries ====
==== Bouncer Entries ====
==== Virus Scan ====
'''not done yet'''
(Might not be able to do this from automation because we don't have a full 3.6-candidates dir)
manually add bouncer entries
 
==== 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 ===
=== Stage and Rename Files ===
Line 85: Line 84:
** Exclude Source packages because they're regenerated for final
** Exclude Source packages because they're regenerated for final
** Exclude *SUMS* because we'll be regenerating them.
** Exclude *SUMS* because we'll be regenerating them.


=== Other Verifications ===
=== Other Verifications ===
==== Virus Scan ====
'''not done yet'''
Manually trigger on stage with:
<pre>
# ffxbld@stage
python /usr/local/bin/extract_and_run_command.py -j4 clamdscan -m --no-summary -- ~/firefox-4.0
</pre>
==== Verify permissions ====
'''not done yet'''
manually run permission checks on stage


==== Verify contents against RC ====
==== Verify contents against RC ====

Revision as of 20:20, 18 March 2011

Release Engineers

bhearsum, nthomas, jhford

Tracking Bug

bug 642234

Notes

Notify Mirrors

Joduinn sent this on March 16th.

RC1 version

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

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

Source

Forced build on builder page using form 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: <left blank>
     value: <left blank>
prop2 name: <left blank>
     value: <left blank>

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/ .

RC 2 Version

Config Update

not done yet

  • Land config update, reconfig pm01

Automated Parts

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

Tag

not done yet "force build" tag builder with correct properties

Source

not done yet "force build" source builder

Major Update Generation

not done yet manually modify 3.5 -> 3.6rc2build3 and 3.6 -> 3.6rc2build3 snippets to point at non-RC bouncer links, and have non-RC2 appv's.

Bouncer Entries

not done yet manually add bouncer entries

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.


Other Verifications

Virus Scan

not done yet Manually trigger on stage with:

# ffxbld@stage
python /usr/local/bin/extract_and_run_command.py -j4 clamdscan -m --no-summary -- ~/firefox-4.0

Verify permissions

not done yet manually run permission checks on stage

Verify contents against RC

Index Files

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

Push to Mirrors

justdave says that we should push the index.html 6 hours before the rest of the contents, to ensure it gets everywhere ahead of everything else.

Notify AV Vendors

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

Push Major Updates

Remove index 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".

Push to Mirrors

Update Wiki Pages