Releases/Firefox 13.0b4/BuildNotes

From MozillaWiki
Jump to: navigation, 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:

  • bug 755829 - release_sanity.py shouldn't fail on blank lines

Build Engineers

{coop} and {kmoir} - Tracking bug: bug 744593

Signed-off Revision(s)

  1. Build 1: fdf0d6f54fd4

L10N changesets

Instructions on how to get them

Tags

Manually tag the automation code, then record the generated tags below. (details)

Build # Branch, Tags Changeset
1 GECKO130_2012051611_RELBRANCH, FIREFOX_13_0b4_RELEASE FIREFOX_13_0b4_BUILD1 1febdba39b18

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux 20120516113045 linux-ix-slave14 1 hrs, 4 mins, 51 secs
Linux64 linux64-ix-slave21 59 mins, 52 secs
Mac moz2-darwin10-slave42 3 hrs, 25 mins, 54 secs
Windows 20120516113045 w32-ix-slave37 3 hrs, 44 mins, 24 secs

Notes

Build 1

Preparing to start Automation

Release:Release Automation on Mercurial:Documentation#Starting_the_automation detailed instructions

  • Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
  • Reserve slaves, e.g.:
[cltbld@buildbot-master13 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master13 master]$ cat reserved_slaves 
8
  • For build1 only, create a symlink for your $version (eg 11.0b4, 10.0.2esr, 10.0.2, 3.6.27) (until bug 725839 is resolved)
# ffxbld@stage
cd /pub/mozilla.org/firefox/nightly/
mkdir ../candidates/$version-candidates
ln -s ../candidates/$version-candidates $version-candidates


 hg tag -f FIREFOX_13_0b4_{RELEASE,BUILD1}
  • updated and reconfigure the master locally (full reconfig will be done later via fabric)
#cltbld@buildbot-master13
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py --dryrun \
    -u kmoir -V 13.0b4 --branch mozilla-beta --build-number 1 \
    -c release-firefox-mozilla-beta.py \
    --products firefox localhost:9001
  • start automation ← monitor progress on buildbot (e.g. beta)
    • the same command as above but without the "--dryrun"

E-mail Metrics

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

   Firefox,firefox,firefox,13.0b4,13.0

Tag

OK

Bouncer Submitter

OK

Source

OK

Build

Firefox

Firefox repacks

OK

Unittests / Talos

XULRunner

Source

OK

Build

OK

Android Signing

Instructions in MobileSigning

Now run on signing1.

OK

L10N verify

Failed on mac after hy-AM, other platforms okay. This verify step scheduled to be removed (bug 749748), so "mach nicht".

Rest OK

Checksums

OK

Updates

OK

Update verify

OK

Reset reserved slaves

The final release with this naming convention, so just got rid of the file:

    rm reserved_slaves

Check permissions / AV scan

OK

Push to internal mirrors

OK

Final verification

Record receipt of "completed_final_verification" emails (1 per platform)

Going to Beta

Run backupsnip

NOTE: Remember to do this at least 2 hours ahead of the expected "go to beta" email. details

 $ cd /opt/aus2/snippets/staging/
 $ time ~/bin/backupsnip Firefox-13.0b4-build1

Done in 8 minutes

Push to beta

Wait for "go" from release managers
For Firefox:

  • Publish (and record run time here): details
 # ffxbld@aus3-staging.mozilla.org
 $ cd /opt/aus2/snippets/staging/
 $ time ~/bin/pushsnip Firefox-13.0b4-build1
  • on completion, email r-d that VERSION updates are live on the beta channel

pushsnip ran in 6m53.823s; email sent to r-d

For Android: no android this release

Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.