|
|
| Line 4: |
Line 4: |
| = Bugs hit = | | = Bugs hit = |
| Enter any bugs pre-existing or newly discovered and filed during the release: | | Enter any bugs pre-existing or newly discovered and filed during the release: |
| * {{bug|}} - description | | * xulrunner source failed with: |
| | hg -R mozilla-beta bundle --base null -r 08158dc2347a source/xulrunner-12.0b5.bundle |
| * | | * |
|
| |
|
| Line 125: |
Line 126: |
| </pre> | | </pre> |
| * start automation ''← monitor progress on buildbot (e.g. [http://buildbot-master08.build.mozilla.org:8001/waterfall?num_events=10&category=release-mozilla-beta- beta])'' | | * start automation ''← monitor progress on buildbot (e.g. [http://buildbot-master08.build.mozilla.org:8001/waterfall?num_events=10&category=release-mozilla-beta- beta])'' |
| DONE TO HERE
| |
| <i>
| |
|
| |
|
| === E-mail Metrics === | | === E-mail Metrics === |
| | <i> |
| Use the address "metrics-alerts < AT > mozilla < PERIOD > org" | | Use the address "metrics-alerts < AT > mozilla < PERIOD > org" |
| | | Firefox,firefox,firefox,12.0b5,12.0 |
| For 3.6.25 you would send
| | Fennec,firefox-mobile,fennec,12.0b5,12.0 |
| Firefox,firefox,firefox,3.6.25,3.6
| | </i> |
| Firefox,firefox,firefox,3.6.26pre,3.6
| |
| | |
| For non-3.6 releases, we need to include Fennec in the email if we build Fennec.
| |
| | |
| For 9.0b2 it would be
| |
| Firefox,firefox,firefox,9.0b2,9.0
| |
| Fennec,firefox-mobile,fennec,9.0b2,9.0
| |
| | |
| And for 9.0 final it's
| |
| Firefox,firefox,firefox,9.0,9.0 | |
| Fennec,firefox-mobile,fennec,9.0,9.0 | |
| | |
| ESRs look like this:
| |
| Firefox,firefox,firefox,10.0.3,10.0
| |
| Firefox,firefox,firefox,10.0.3esr,10.0
| |
| | |
| === E-mail mirrors@mozilla.org ===
| |
| Not necessary for rapid release betas, files only go as far as the 'internal mirrors'.
| |
| | |
| Coordinate yourself with the person creating the ESR and the latest release which normally go out at the same time.
| |
| | |
| They want to know approximately what time push to external mirrors will occur. Ideally this is a 24hr notice to them, with the estimated time.
| |
| <pre> | |
| Subject: Firefox {VERSION1} [and {VERSION2}] coming to mirrors on {DATE}
| |
| Body:
| |
| We're planning on pushing our Firefox {VERSION1} [and {VERSION2}] release(s) to mirrors 24 hours before {DATE}.
| |
| # If this is a chemspill, please mention that in the email as it will mean pinging
| |
| # for CDN to be enabled when the push to internal mirrors happens
| |
| | |
| If you believe these releases or these dates will cause any problems,
| |
| please notify release at mozilla.com. If you have any problems with mirror
| |
| status/weights/etc, please notify mirror-submissions at mozilla.org.
| |
| </pre>
| |
| | |
| === Edit rsync exclude files ===
| |
| Edit /pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude on stage so that it excludes the current release. This prevents external mirrors from picking up the new release prematurely.
| |
| | |
| For rapid release betas, this is not necessary as there's already an exclude that matches beta releases.
| |
|
| |
|
| === Tag === | | === Tag === |
| | No problems. |
|
| |
|
| === Bouncer Submitter === | | === Bouncer Submitter === |
| | | TODO |
|
| |
|
| === Source === | | === Source === |
| | | No problems. |
| | |
| === Start autosign ===
| |
| NOTE: use new signcode keys from d:/2011-keys
| |
| | |
| Instructions are in [https://intranet.mozilla.org/RelEngWiki/index.php/Signing#.22autosign.22.2C_used_for_Firefox_3.6.x.2C_10.0.x.2C_and_10.0.x_ESR Signing]
| |
|
| |
|
| === Build === | | === Build === |
| | DONE TO HERE |
| | <i> |
| ==== Firefox ==== | | ==== Firefox ==== |
|
| |
|
| Line 201: |
Line 161: |
|
| |
|
| === XULRunner === | | === XULRunner === |
| | ====Source==== |
| | It timed out: |
| | hg -R mozilla-beta bundle --base null -r 08158dc2347a source/xulrunner-12.0b5.bundle |
| | I re-triggered it. Let's see how it goes. |
|
| |
|
| ====Source====
| | TODO check |
|
| |
|
| ====Build==== | | ====Build==== |
| Line 230: |
Line 194: |
|
| |
|
| ==== Update verify ==== | | ==== Update verify ==== |
|
| |
| === Major Update ===
| |
| Major update generation is not kicked off automatically. You should only create them once the final builds for the "latest" build are ready.
| |
| For instance, the 3.6.26 builds got created a week before the 10.0 release but the "final" 10.0 builds were not created after few days.
| |
|
| |
| Follow instructions from the [[Release:Release_Automation_on_Mercurial:Documentation#Major_Update_.28Firefox_only.29|Major update]] documentation.
| |
|
| |
| ==== Major Update verify ====
| |
|
| |
|
| === Reset reserved slaves === | | === Reset reserved slaves === |
| Line 245: |
Line 201: |
| It is supposed to be triggered automatically after updates are done. | | It is supposed to be triggered automatically after updates are done. |
| File a bug if it doesn't. <small>[[Release:Release_Automation_on_Mercurial:Documentation#Antivirus_check|details]]</small> | | File a bug if it doesn't. <small>[[Release:Release_Automation_on_Mercurial:Documentation#Antivirus_check|details]]</small> |
|
| |
| === Push to internal mirrors ===
| |
| This is done by automation for rapid release betas.
| |
|
| |
| For other releases, this should be done manually at this point, after check permissions / AV scan have completed.
| |
| * Make sure the rsync excludes have been updated ([[Releases/BuildNotesTemplate#Edit_rsync_exclude_files]])
| |
| * Force build the push to mirrors builder. Make sure at least 15 minutes have elapsed since editing the rysnc module to give it time to sync out.
| |
|
| |
| [https://intranet.mozilla.org/ReleaseEngineering/Release/Primer#Mirrors_.28internal_.26_external.29 Mirrors Policy]
| |
|
| |
|
| === Going to Beta === | | === Going to Beta === |