Releases/Firefox 3.6.26/BuildNotes

From MozillaWiki
Jump to navigation Jump to search

Notes About Releasing

Please update the Notes Template and the Release:Primer for future releases (bug fixes, changes to automation) as needed

Bugs hit

Enter any bugs pre-existing or newly discovered and filed during the release:

  • I landed my changes on default and forgot to merge to production before tagging the repos
    • release_sanity saved the day and I fixed it before starting anything

Build Engineers

armenzg - Tracking bug: bug 719214

Signed-off Revision(s)

Build 1: 173bc943fe0d

L10N changesets

Instructions on how to get them

  • Firefox: [1]
  • Fennec: N/A

Tags

Build # Branch, Tags Changeset
MOBILE80_#_RELBRANCH, FENNEC_VERSION_RELEASE, FENNEC_VERSION_BUILD1 #
GECKO80_#_RELBRANCH, FIREFOX_VERSION_BUILD1 FIREFOX_VERSION_RELEASE #

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux 20120124074252 mv-moz2-linux-ix-slave04
Mac bm-xserve11
Windows mw32-ix-slave03

Notes

Build 1

Preparing to start Automation

  • Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
    • "any master", "1.9.2", "any builder"
  • Reserve slaves
echo 10 > /builds/buildbot/build1/master/reserved_slaves_bm08-build1
  • Update l10n changesets for desktop, mobile
  • Land automation configs
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags
    • FIREFOX_3_6_26_{RELEASE,BUILD1}
  • update and reconfigure the master
    • cd /builds/buildbot/build1
    • make update && make reconfigure
  • start automation
 cd /builds/buildbot/build1/master
 source ../bin/activate
 PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -p firefox -V 3.6.26 --branch  mozilla-1.9.2 --build-number 1 -c release-firefox-mozilla-1.9.2.py --dryrun localhost:9001

The real thing: 

cd /builds/buildbot/build1/master
 source ../bin/activate
 PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -p firefox -V 3.6.26 --branch  mozilla-1.9.2 --build-number 1 -c release-firefox-mozilla-1.9.2.py localhost:9001

DONE TO HERE

E-mail Metrics

Use the address "metrics-alerts < AT > mozilla < PERIOD > org"

For 3.6.25 you would send 

Firefox,firefox,firefox,3.6.25,3.6
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

E-mail mirrors@mozilla.org

Not necessary for rapid release betas, files only go as far as the 'internal mirrors'.

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. 

Subject: Firefox {VERSION} coming to mirrors tomorrow
Body:
We're planning on pushing our Firefox {VERSION} release to mirrors sometime over 
the next 24 hours in time.
# 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.

Tag

Bouncer Submitter

Source

Start autosign

NOTE: use new signcode keys from d:/2011-keys

Instructions are in CombinedSigning

Build

Firefox

Firefox repacks

Fennec

Android
Desktop Builds
Mobile Desktop repacks

Unittests / Talos

  1. Look to see that they ran
  2. Document any oranges (per platform) for unittests - if possible, try to confirm it's known/random
  3. Make sure there's no red/failures that we need to have a dev look at

XULRunner

Source

Build

Signing

NOTE: use new signcode keys from d:/2011-keys and QUIT SIGNCODE when you're done with keymaster

Partner Repack

Firefox

Fennec

Firefox Signing

Android Signing

Instructions in MobileSigning

NOTE: It can be started in a different Windows without having to wait for Firefox signing to finish.

Android Signature Verification

L10N verify

Updates

Update verify

Major Update

Update verify

Socorro Product Data Updates

Reset reserved slaves

This is also a good time to QUIT SIGNCODE on keymaster if you've still got it running.

Run backupsnip

Check permissions / AV scan

Push files to internal mirrors

Mirrors Policy

Final verification

Push to beta

Push index file to mirrors

Push to external mirrors

if this is a chemspill you will want to ping justdave (or other sysadmin) in #release-drivers 
and ask them to enable CDN

Publish Fennec to the Android Market

Push the files

  • edit push_fennec_{beta,release}.sh as ffxbld@stage
  • run push_fennec_{beta,release}

Android Market

IMPORTANT - Make sure to follow instructions!

  • download multi apk (e.g. multi/fennec-8.0b4.multi.eabi-arm.apk)
  • visit https://market.android.com/publish
  • choose "Firefox Beta" or "Firefox"
  • select the "APK Files" tab and choose "Upload APK"
    • choose the multi apk that you downloaded and hit "upload"
      • NOTE: the progress bar does not seem to show progress (at least on Google Chrome)
    • when it finishes uploading, verify VersionCode is build date
    • hit "Save"
  • activate new apk (You should see an Error message since both apk's are active)
  • deactivate old apk (You should not see the Error message anymore)
  • hit "Save"
  • If this is a beta 1, go to "Product Details" tab -> Recent Changes, change the url to http://www.mozilla.com/en-US/mobile/{VERSION}beta/releasenotes/
    • and hit "Save"

Push XULRunner to Mirrors

Update XULRunner wiki page

For major releases or chemspills, update the links on:

Push to Release Channel

Update symlinks

Once we're signed off on the release channel.

Remove index.html files

If you created them earlier to hide the release.

Update browser choice website

Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Firefox_3.6.26/BuildNotes&oldid=389752"