SeaMonkey:Release Process:2.4b3

From MozillaWiki
Jump to: navigation, search

« SeaMonkey 2.4b3

Build Harness

SeaMonkey:Release Automation


Tracking bug filed as bug 687205

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
  • First release build since updating the buildmaster dir setup.


  • Made sure all build machines have clean release directories.
    • Actually done due to the buildmaster work.
  • Updated build/buildbot-configs 85be25491891 for l10n and configs
  • Updated and reconfigured buildmaster
  • Kicked off with the following command:
../bin/buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-beta -c "SeaMonkey 2.4b3build1" doit
  • Tagging and Builds finished fine
  • L10n Repacks for windows, failed about half the locales. Due to (somehow) missing clobbering release dirs on one of the windows slaves.
    • ReKicked via the script (See Also Log)
  • These repacks finished fine

Update Version for stage scripts

On, modified ~/ for the current release run.


  • 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 lots of expected changed strings.
  • Update and Update verification were both good.

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 website updates Live


cvs up -Pd && patch -p0 < patch && cvs ci -m ....

Push Updates to the beta Channel

Once website updates are live

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

~/bin/backupsnip Sea*2.4b1*build1
~/bin/pushsnip Sea*2.4b1*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.

Send Announce

Send the announcement to newsgroups and about-mozilla in one e-mail, send to announce@ in another.

Correctly Push Updates to the beta Channel

IanN pointed out that updates were not live yet, and I noticed that I ended up not pushing 2.4b3 out properly, so redid with the following command

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

~/bin/backupsnip Sea*2.4b3*build1
~/bin/pushsnip Sea*2.4b3*build1