Releases/Firefox 4.0/BuildNotes: Difference between revisions
< Releases | Firefox 4.0
Jump to navigation
Jump to search
(→Tag: this info was already in log) |
No edit summary |
||
| Line 9: | Line 9: | ||
Joduinn sent this on March 16th. | Joduinn sent this on March 16th. | ||
== Config Update == | == RC1 version == | ||
=== Config Update === | |||
[http://hg.mozilla.org/build/buildbot-configs/rev/0781df67af87 This small update to the release config] was landed. | [http://hg.mozilla.org/build/buildbot-configs/rev/0781df67af87 This small update to the release config] was landed. | ||
== Automated Parts == | === Automated Parts === | ||
Some of this release-day work makes sense to do from the release automation. Use force build for these. | Some of this release-day work makes sense to do from the release automation. Use force build for these. | ||
=== Tag === | ==== Tag ==== | ||
forced build using the webform with values | forced build using the webform with values | ||
your name: jhford | your name: jhford | ||
| Line 27: | Line 28: | ||
value: mozilla/release-firefox-mozilla-2.0.py | value: mozilla/release-firefox-mozilla-2.0.py | ||
=== Source === | ==== Source ==== | ||
Forced build on builder page using form values | Forced build on builder page using form values | ||
your name: jhford | your name: jhford | ||
| Line 40: | Line 41: | ||
value: <left blank> | value: <left blank> | ||
= | === Stage and Rename Files === | ||
== Stage and Rename Files == | |||
Summary: | Summary: | ||
* Copy files to ~ffxbld and rename to non-RC versions | * Copy files to ~ffxbld and rename to non-RC versions | ||
| Line 64: | Line 57: | ||
</pre> | </pre> | ||
== | == RC 2 Version == | ||
After we did some of the work against RC1, we respun, and had to start this work again. | |||
Revision as of 18:06, 18 March 2011
Release Engineers
bhearsum, nthomas, jhford
Tracking Bug
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
After we did some of the work against RC1, we respun, and had to start this work again.