SeaMonkey:Release Process:2.3b2

From MozillaWiki
Jump to: navigation, search

« SeaMonkey 2.3b2

Build Harness

SeaMonkey:Release Automation


Tracking bug filed as bug 675528

Build Engineer

Justin Wood

Signed-off Revisions


L10n revisions according to opt-ins as taken from the sign-off tool (and pushed ship-it)


  • Have to do the same s/mac/mac64/ work as in SeaMonkey 2.1b2. Will have to look into an easier way for that
  • Adds two locales (gl and zh-CN)


  • Made sure all build machines have clean release directories.
    • Manually on windows, jumphost sh
  • Updated build/buildbot-configs 1652654d6479 for l10n and configs
  • Updated and reconfigured buildmaster
  • Kicked off with the following command:
buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-beta -c "SeaMonkey 2.2b2build1" doit
  • Tagging failed (on a hg out for pt-PT which is ignorable) Decided to officially support skip_tag with build/buildbot-configs a5b0f92b8c17
  • Reconfigured and kicked with
buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-beta -c "SeaMonkey 2.2b2build1" doit
  • All build succeeded normally
  • Had issues with pt-PT locale on linux, due to cz string changes that I missed in l10n signoff (I took the changes myself for b1)
    • retagged in time to catch mac/win and re-kicked linux

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

  • _l10n_verify and updates started automatically, triggered by the fake-signing.
    • L10n verification is mostly useless, since we have new locales, and lots of expected changed strings.
  • update failed, due to the build machine putting snippets in aus2.beta/ rather than aus2/ Unsure where in the chain this bug is hiding, but fixed manually with the following command (after logging into the machine/build):
rsync -av -e "ssh -oIdentityFile=~/.ssh/seabld_dsa" aus2.beta/
  • the Update verification was good on all platforms

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

Used as documented in 2.0.3 notes to finally push the files to the public dir for mirrors to pick them up.

Final Verification

Used 'Force Build' to start the final_verification builder; all tested URLs are HTTP 200 and 302 - ready for going public!

Push Updates to the beta Channel

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

~/bin/backupsnip Sea*2.1rc1*build1
~/bin/pushsnip Sea*2.1rc1*build1


Push build to TrendMicro

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