SeaMonkey:Release Process:2.4

From MozillaWiki
Jump to: navigation, search

« SeaMonkey 2.4

Build Harness

SeaMonkey:Release Automation


Tracking bug filed as bug 688682

Build Engineer

Justin Wood

Signed-off Revisions


L10n revisions based on milestone 2.4 beta 4. (Firefox took updates, so we did as well, de and sk to be exact)


  • Have to do the same s/mac/mac64/ work as in SeaMonkey 2.1b2. Will have to look into an easier way for that
  • Accidentally left the version-bump enabled, happily chugged along as a no-op.


  • Made sure all build machines have clean release directories.
    • Manually on windows, jumphost sh
  • Updated build/buildbot-configs f1573637ff3f for l10n and configs
  • Updated and reconfigured buildmaster
  • Kicked off with the following command:
(cd /builds/buildbot/master01/master && ../bin/buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.4build1" doit)
  • Tagging completed fine
  • All builds finished fine.
  • All repacks finished fine.

Fake tr locale

Not Needed for this build


  • 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.
    • Logged onto and ran sh ~/
    • which moves all mac64 files/directories to mac, and removes the mac64 dir.
  • 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 and ran sh ~/

Updates and Verification

  • Updates failed, due to still having 2.4b3 as the old version listed, not 2.3.3
    • Updated build/buildbot-configs 0e82085e62cb
    • Updated and reconfigured buildmaster
    • Clobbered updates/verifications on the relevant machines
  • Restarted update and l10n_verify via web interface

Updates on release channel to 2.4

  • Update finished ok
  • Verifications finished ok

Updates from beta's to 2.4

  • Update snippets were generated from release config for beta channel, but will not be used (to match firefox)

Copy Language Packs

Used as documented in 2.0b1 notes to move the langpacks into the directory we want them in for release.


Used as documented in 2.0b1 notes to move the Windows zips into the directory we want them in for release.

Create Checksums

With as documented in 2.0.3 notes, created MD5SUMS and SHA1SUMS files containing all files we release - copying the README from last time and replacing the versions as needed, as well as doing the same for Linux x86_64.

Push To Mirrors

  • With our Bouncer bug, MoCo set us up to be internal mirrors only, so pushing there as soon as we are ready here.
  • Used as documented in 2.0.3 notes to finally push the files to the public dir for mirrors to pick them up.

Push Updates to the beta Channel

Not being done

Final Verification

  • Used 'Force Build' to start the final_verification builder;
  • almost all tested URLs are HTTP 200 and 302
  • Failed for partials, reopened by bouncer bug since I noticed I mistyped 2.2 instead of 2.3.3 as previous version (copy/paste fail on local replace script) Once that is fixed, I'll just have to re-run the verification/check sentry


Update Patcher-Configs

  • For 2.0.14->2.4 MU we need to update Patcher Configs moz191-seamonkey-branch-major-patcher2.cfg
    • Replaced all refs of 2.3.3 to 2.4 in <current-update>...</current-update>
    • Replaced block of <2.3.3>...<2.3.3> in past updates with the block for 2.4 from mozRelease-seamonkey-branch-patcher2.cfg so that buildID's and URLs are all correct.
  • Checked in:
$ cvs ci -m "Bug 688958, update patcher-configs for 2.4 MU"
Checking in moz191-seamonkey-branch-major-patcher2.cfg;
/cvsroot/mozilla/tools/patcher-configs/moz191-seamonkey-branch-major-patcher2.cfg,v  <-- 
new revision: 1.15; previous revision: 1.14

Update Buildbot Configs

  • Updated build/buildbot-configs 99cbaabcd926 to point at the 1.9.1 based config as our primary, and to update the lines for 2.4 MU.
  • Updated and reconfigured buildmaster
    • Ran into error on reconfig, due to new master setup (1.9.1 config points at l10n-changesets and I never symlinked that, fixed with a symlink)

Run MU Builder

  • On web interface for major-update and hit the Force Build button.
    • No Problems (Expected |ka| verification failure, due to no ka locale on 2.4)

Go To Full Mirror Network

File a bug to get releng to make SeaMonkey 2.4 go to full mirror network. Use bug 678986 as a reference.

Push Updates to the release Channel

2.3 to 2.4

Note use SeaMonkey-2.4-build1

On aus |/opt/aus2/snippets/staging/|:

~/bin/backupsnip SeaMonkey-2.4-build1
~/bin/pushsnip SeaMonkey-2.4-build1

2.0.14 to 2.4

Note use SeaMonkey-2.0.14-build2-2.4-build1-MU

On aus |/opt/aus2/snippets/staging/|:

~/bin/backupsnip SeaMonkey-2.0.14-build2-2.4-build1-MU
~/bin/pushsnip SeaMonkey-2.0.14-build2-2.4-build1-MU

Push build to TrendMicro

I used the TrendMicro provided staging ftp directory to stage 2.4 en-us win32 for them to scan, and be sure there are no false-positives.


  • Send announcement to mailing lists/newsgroups
  • Post announcement on SeaMonkey Blog