Releases/Firefox 9.0b6/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 177: Line 177:


=== Partner Repack ===
=== Partner Repack ===
==== Firefox ====
N/A
==== Fennec ====


=== Firefox Signing ===
=== Firefox Signing ===

Revision as of 23:09, 14 December 2011

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:

Build Engineers

lsblakk - Tracking bug: bug 700907

Signed-off Revision(s)

Build 1: d2f1a400e430

L10N changesets

Instructions on how to get them

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
Linux64
Mac
Windows

Fennec

Build # Type Build ID Build machine Time to build
1 android
linux
macosx
win32

Notes

Build 1

Syncing repos

N/A

Diff mozconfigs

N/A

Preparing to start Automation

  • Set clobbers for the appropriate masters. Any master, mozilla-beta, any builder.
  • Reserve slaves
[cltbld@buildbot-master08 ~]$ echo 8 > /builds/buildbot/build1/master/reserved_slaves_bm08-build1
  • Updated l10n changesets for desktop, mobile
  • Landed automation configs on both default/production
  • Tagged buildbot-configs, buildbotcustom, & tools with build & release tags
hg tag -f FIREFOX_9_0b6_RELEASE FIREFOX_9_0b6_BUILD1 FENNEC_9_0b6_BUILD1 FENNEC_9_0b6_RELEASE
  • updated and reconfigured the master
  • dry run of automation
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u lsblakk -pfirefox,fennec 
-V 9.0b6 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py 
-c release-fennec-mozilla-beta.py --dryrun localhost:9001
  • started automation
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u lsblakk -pfirefox,fennec 
-V 9.0b6 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py 
-c release-fennec-mozilla-beta.py localhost:9001

E-mail Metrics

Firefox,firefox,firefox,9.0b6,9.0
Fennec,firefox-mobile,fennec,9.0b6,9.0

Tag

Firefox mv-moz2-linux-ix-slave07 - No problems Fennec mv-moz2-linux-ix-slave21 - No problems

Bouncer Submitter

No problems

Source

No problems

Start autosign

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

PRODUCT=firefox
VERSION=9.0b6
BUILD=1
TAG=FIREFOX_9_0b6_RELEASE
REPO='releases/mozilla-beta'
EMAIL=release@mozilla.com
KEYDIR=d:/2011-keys
RELCONFIG=mozilla/release-firefox-mozilla-beta.py

cd ${HOME}/hg-tools/ # if it exists, otherwise create a fresh clone
hg pull && hg up -r ${TAG}
mkdir -p ~/signing-work/${PRODUCT}-${VERSION}/lib/python
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .
rsync -av ~/hg-tools/lib/python/ ./lib/python/
make autosign PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} \
 EMAIL=${EMAIL} KEYDIR=${KEYDIR} RELCONFIG=${RELCONFIG}

Build

Firefox

No problem

Firefox repacks

No problem

Fennec

Android

No problem

Desktop Builds

No problem

Mobile Desktop repacks

No problem

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

No problem

Build

No problem

Signing

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

Partner Repack

N/A

Firefox Signing

Signing sent out an email saying it had started at 12:08 PT but then nothing after that, on the keymaster my cygwin window was gone and signcode was not running. Went on to keymaster and removed the contents of ~/signing-work/firefox-9.0b6 and started again:

PRODUCT=firefox
VERSION=9.0b6
BUILD=1
TAG=FIREFOX_9_0b6_RELEASE
REPO='releases/mozilla-beta'
EMAIL=release@mozilla.com
KEYDIR=d:/2011-keys
RELCONFIG=mozilla/release-firefox-mozilla-beta.py

mkdir -p ~/signing-work/${PRODUCT}-${VERSION}/lib/python
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .
rsync -av ~/hg-tools/lib/python/ ./lib/python/
make autosign PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} REPO=${REPO} \
 EMAIL=${EMAIL} KEYDIR=${KEYDIR} RELCONFIG=${RELCONFIG}

Android Signing

No email was sent out because of bug 708859 (I hadn't pulled this into my buildbotcustom when I reconfiged the masters)

Android Signature Verification

Triggered manually with who set to the path to en-US/multi apks - no problems.

L10N verify

Updates

Update verify

Major Update

Update verify

Socorro Product Data Updates

Reset reserved slaves

Reset reserved slaves file to 0.

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

run push_fennec_{beta,release}.sh on stage

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

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