SeaMonkey:Release Process:2.5b1
Build Harness
Bugs
Tracking bug filed as bug 688952
Build Engineer
Justin Wood
Signed-off Revisions
- releases/comm-beta
- e47b99c61e4d
- releases/mozilla-beta
- FIREFOX_8_0b1_BUILD1
(GECKO80_2011092805_RELBRANCH)
- dom-inspector
- DOMI_2_0_10_RELEASE
(DOMI_2_0_10)
- chatzilla
- SEA_2_5_BASE
- venkman
- 65b690f78f60
L10n revisions according to opt-ins as taken from the sign-off tool (and pushed ship-it)
Notes
- Have 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.
- Updated build/buildbot-configs 37c4b9cc5bff 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.5b1build1" doit
- Tagging finished fine.
- Builds/Repacks were going ok, but I noticed we did not have enough repacks, and caught that shipped-locales was missing many locales.
- Gecko 7.0.1 chemspill caused cutoff.
Build2
Changesets
- Pushed shipped-locales changes to all branches
- Transplanted newer comm-beta csets to our 2.5b1 relbranch
- Updated all repo's to have a relbranch specified.
- L10n needed
default
specified since our relbranch was not yet created on the new ones.
- L10n needed
- New Cset was only for comm, and is: releases/comm-beta 53d898956880
- Config changes at: buildbot-configs
Build
- Made sure all machines have clean release directories.
- 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.5b1build1" doit
- Builds and Tagging finished fine.
- Repacks went ok, except one run on linux (tr).
- Retriggered per buildbot web UI. Went good.
Update Version for stage scripts
On stage-old.mozilla.org, modified ~/versions.sh for the current release run.
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.
- Logged onto stage-old.mozilla.org and ran
sh ~/mac64tomac.sh
- which moves all mac64 files/directories to mac, and removes the mac64 dir.
- Logged onto stage-old.mozilla.org and ran
- 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
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 langpackmove.sh
as documented in 2.0b1 notes to move the langpacks into the directory we want them in for release.
Zipcopy
Used zipcopy.sh
as documented in 2.0b1 notes to move the Windows zips into the directory we want them in for release.
Create Checksums
With make-checksums.sh
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 mirrorpush.sh
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
locally:
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.5b1*build2 ~/bin/pushsnip Sea*2.5b1*build2
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.
- Created |viruspush.sh| on staging for this for future.
Send Announce
Send the announcement to newsgroups and about-mozilla in one e-mail, send to announce@ in another.