SeaMonkey:Release Process:2.1b3

From MozillaWiki
Revision as of 19:30, 6 April 2011 by Callek (talk | contribs)
Jump to navigation Jump to search

« SeaMonkey 2.1b3

Build Harness

SeaMonkey:Release Automation

Bugs

Tracking bug filed as bug 647928

Build Engineer

Justin Wood

Signed-off Revisions

comm-central
4af4a784e99c (Built with)
efa612d2641a (Updated shipped-locales and moved tags)
releases/mozilla-2.0
b5a576b9a3e0
dom-inspector
0bb7db177214
chatzilla
3cf0c028cc0a
venkmman
3cf0c028cc0a

L10n revisions according to opt-ins as listed in l10n-changesets (taken from the sign-off toolBug 647637 c#2)

Notes

  • SeaMonkey 2.1b3 is Feature and String freeze for the 2.1 series, based on Gecko 2.0 (off the releases/mozilla-2.0 branch)
  • Had to do the same s/mac/mac64/ work as in SeaMonkey 2.1b2. Will have to look into an easier way for that

Build

  • Made sure all build machines have clean release directories. (Done via clobberer, then decided I did not want to risk that still being broken, and did it manually too)
  • Updated l10n-changesets and release-config.py
  • Updated and reconfigured buildmaster
  • Kicked off with the following command:
buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-1.9.1 -c "SeaMonkey 2.1b3build1" doit
  • Did the wrong --branch here, but caught that and fixed. But before I re-sent I noticed that I didn't update the buildbot branch for comm-2.0 anyway (xref)
    • Updated and Reconfigured for that.
  • Kicked off with the following command:
buildbot sendchange --username=Callek --master=localhost:9010 --branch=comm-central -c "SeaMonkey 2.1b3build1" doit
  • Had a bad cZ changeset entered (copy/paste error), fixed in new push
    • Updated and Reconfigured for that.
  • Kicked off again with the following command:
buildbot sendchange --username=Callek --master=localhost:9010 --branch=comm-central -c "SeaMonkey 2.1b3build1" doit
  • We failed three of our signed off locales, nb-NO, fi, sv-SE. Holding next steps until I get an ok to ship without them (from our l10n coordinator)
    • Got an OK from KaiRo for moving forward with this, had to update shipped-locales due to the failure here (See new cset above), I moved the tags so that we don't need a build2.

Signing

  • Our mac builds (non en-US) uploaded to mac64/ so I had to move them over to mac/ on stage, for both updates and builds.
    • From build1 dir: rsync -av mac64/ mac/ and rm -rf mac64
    • From updates dir: rsync -av mac64/ mac/ and rm -rf mac64
  • We have no signing infrastructure for SeaMonkey right now, so I faked the signing step that is usually done after completion of builds and L10n repacks and before the update generation.
  • Logged onto stage-old.mozilla.org and ran sh ~/fakesign.sh


Wall Clock Time

Build

  • buildbot sendchange: Tue Apr 5 22:24:52 PDT 2011
  • tag:
  • source:
  • linux_build:
  • linux64_build:
  • win32_build:
  • macosx_build:
  • linux_repack (23 locales):
  • win32_repack (23 locales):
  • macosx_repack (23 locales):
  • updates:

Verification

  • linux_l10n_verification:
  • win32_l10n_verification:
  • macosx_l10n_verification:
  • linux_update_verify:
  • win32_update_verify:
  • macosx_update_verify:
  • final_verification:

Update Channels

  • Push to beta:
  • Push to mirrors:
  • Push to release:
Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey:Release_Process:2.1b3&oldid=296474"